Re: Can we remove support for standard_conforming_strings = off yet?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Julien Rouhaud <rjuju123(at)gmail(dot)com>, John Naylor <johncnaylorls(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Can we remove support for standard_conforming_strings = off yet?
Date: 2026-01-21 20:25:16
Message-ID: aXE2LFYoLE-b0k1K@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 21, 2026 at 03:09:30PM -0500, Tom Lane wrote:
> Julien Rouhaud <rjuju123(at)gmail(dot)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 = 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.

Great, thanks.

--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com

Do not let urgent matters crowd out time for investment in the future.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Corey Huinker 2026-01-21 20:42:21 Re: Extended Statistics set/restore/clear functions.
Previous Message Robert Haas 2026-01-21 20:25:00 Re: pgsql: tests: Add a test C++ extension module