Date: Mon, 5 Jan 2026 20:01:15 +0800
From: Julien Rouhaud <rjuju123@gmail.com>
To: John Naylor <johncnaylorls@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Andrew Dunstan <andrew@dunslane.net>,
	pgsql-hackers@lists.postgresql.org
Subject: Re: Can we remove support for standard_conforming_strings = off yet?
Message-ID: <aVuoC2zL3DA8tgOT@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>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CANWCAZZXQuxy44h5aZbNVjei9nsN_FmHMDnvN4YpyEpiCmmcow@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/aVuoC2zL3DA8tgOT%40jrouhaud>
Precedence: bulk

On Mon, Jan 05, 2026 at 05:03:48PM +0700, John Naylor wrote:
> On Thu, Jan 1, 2026 at 12:04 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Personally I would call it a deal-breaker if I thought it'd affect
> > more than a very very tiny number of people.  But the entire premise
> > of this patch is that nobody is using standard_conforming_strings =
> > off in production anymore.  If that isn't true it's probably a
> > mistake to go forward anyway.
> 
> FWIW, I spent a few minutes looking, and I only found issues from ~5
> years ago about software not working with the setting off. I didn't
> see any details on what they were running in the application stack
> that required it:
> 
> https://github.com/PostgREST/postgrest/issues/1992
> 
> https://github.com/npgsql/npgsql/issues/3333

I had another one ~4 years ago:

https://github.com/powa-team/powa-archivist/issues/51

Since I fixed powa-archivist at that time, I don't know if anyone else would
have faced the same problem, although the OP is likely still using the same
setting.