Julien Rouhaud <[email protected]> writes:
> On Tue, Jan 20, 2026 at 01:31:53PM -0500, Tom Lane wrote:
>> So, nobody's actually spoken against this change. I think we should
>> go forward with it, for the reasons I gave at the top of the thread
>> and because "if not now, when?". I have little doubt that if there
>> is anyone still running with standard_conforming_strings = off, they
>> aren't going to change until forced to. So unless we want to live
>> with the potential security hazard forever, we're going to have to
>> make a breaking change sometime.
> +1 from me. All of that is sensible, plus from an extension point of view
> it's
> easy to write code that is broken with standard_conforming_strings = off so
> it's one less thing to worry about.
Pushed.
regards, tom lane
