model-writtenrun 6967 - may be wrong, links go to the source messages. Commit-by-commit LLM analysis is in the Commits dialog.
- Tom Lane proposed permanently enabling standard_conforming_strings to eliminate escaping-related security hazards and parser dependence on a changeable setting, while retaining the parameter for clients to query or set to on; Pavel Stehule supported the proposal #1 #2.
- Tom submitted four patches covering enforcement, server cleanup, pg_dump and pg_dumpall changes, and removal of escape_string_warning; he also corrected his initial expectation of substantial lexer savings because escape-string syntax still needs the same lexer rules #3.
- The submission identified an upgrade hazard for existing dumps made with standard_conforming_strings off, proposed forcing it on when making new dumps, and preserved pg_restore's handling of old archives for older destination servers; Tom floated landing only the dump changes first if compatibility concerns required delaying enforcement #3.
- Corey Huinker suggested a transitional allowance or an intermediate-server restoration workflow, while Andrew Dunstan questioned whether old dumps were guaranteed compatible; Tom stressed preserving potentially irreplaceable backups and said proceeding depended on the affected population being very small #4 #5 #6.
- Tom separately removed a misleading composite-value escaping note in d6542f8dfc; that cleanup originated in thread #77921, with this thread providing context about retiring nonstandard strings, and was not part of the attached series #3.
- Corey subsequently reported finding no missed removals, accepted deleting escape_string_warning despite some compatibility unease, and requested release notes explaining that affected old dumps need restoration through a pre-19 server #8.
- John Naylor and Julien Rouhaud supplied historical examples of applications encountering the off setting, with Julien noting that an affected installation might still use it #9 #10.
- Tom concluded that delaying would not induce remaining users to migrate and that the security hazard justified proceeding; David G. Johnston and Julien endorsed the decision, with Julien highlighting simpler extension correctness #11 #12 #13.
- Tom announced the push of 4576208454, which combines all four patches from #3 without content changes, completing the submitted series #14.
- After the landing, jian he proposed initializing AH->public.std_strings to true in _allocAH to avoid an attempted SET standard_conforming_strings = off after OpenArchive; the thread ends without a response or demonstrated fix for that follow-up #16.