From: Tom Lane <tgl@sss.pgh.pa.us>
To: Julien Rouhaud <rjuju123@gmail.com>
cc: John Naylor <johncnaylorls@gmail.com>,
        Andrew Dunstan <andrew@dunslane.net>,
        pgsql-hackers@lists.postgresql.org
Subject: Re: Can we remove support for standard_conforming_strings = off yet?
In-reply-to: <aXCrK7vsVSNPWKui@jrouhaud>
References: <3279216.1767072538@sss.pgh.pa.us> <3730915.1767135010@sss.pgh.pa.us> <ab7d1d7f-7474-4735-860f-5de190cb31f8@dunslane.net> <3924010.1767200681@sss.pgh.pa.us> <CANWCAZZXQuxy44h5aZbNVjei9nsN_FmHMDnvN4YpyEpiCmmcow@mail.gmail.com> <aVuoC2zL3DA8tgOT@jrouhaud> <1706007.1768933913@sss.pgh.pa.us> <aXCrK7vsVSNPWKui@jrouhaud>
Comments: In-reply-to Julien Rouhaud <rjuju123@gmail.com>
	message dated "Wed, 21 Jan 2026 18:32:11 +0800"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2402301.1769026170.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 21 Jan 2026 15:09:30 -0500
Message-ID: <2402302.1769026170@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/2402302.1769026170%40sss.pgh.pa.us>
Precedence: bulk

Julien Rouhaud <rjuju123@gmail.com> 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 =3D 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 vi=
ew it's
> easy to write code that is broken with standard_conforming_strings =3D o=
ff so
> it's one less thing to worry about.

Pushed.

			regards, tom lane