Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vielp-00CTCX-1J for pgsql-hackers@arkaria.postgresql.org; Wed, 21 Jan 2026 20:25:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vielo-009A8s-1u for pgsql-hackers@arkaria.postgresql.org; Wed, 21 Jan 2026 20:25:40 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vielV-0097In-2p for pgsql-hackers@lists.postgresql.org; Wed, 21 Jan 2026 20:25:22 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vielU-001mRD-08 for pgsql-hackers@lists.postgresql.org; Wed, 21 Jan 2026 20:25:21 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2026010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=ufd4L5KTC4g94SUmhM/6guBJNir6ESxeBnbX23K7XJI=; b=cz/Qi SpznPAoQigYSQyoJCJA1xjEk0mg+8ekV/kBoUXwMtJ75EGl2l+LKjWokeDQebpxCPaKjWU2sbvSKn FoFeqvT1jDsrSXbKOJQNkyBIBm01mrBhU+uV7ob0IAxWP2W9dys4OQC2j68ico5GZ8X3K25UK9KWQ HgJnRaGMwteHWD0PcMfOT6MesB7UMmsftcfyyT68RV2vcaKDWm1QzqdoGAKt+aY7EzVj2SHIWZJ8h 7tnHSgMVZqXLG5B5n7e4QSundZzJD5MVLxCCliNBBxVN3pSKzMPKx6QPqRmBchpiEK5NKwN/SzfEe BXlLfRHh8lYnxtFGnLRqDJiRUZ0KA==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1vielQ-0000000FkMl-3L8L; Wed, 21 Jan 2026 15:25:16 -0500 Date: Wed, 21 Jan 2026 15:25:16 -0500 From: Bruce Momjian To: Tom Lane Cc: Julien Rouhaud , John Naylor , Andrew Dunstan , pgsql-hackers@lists.postgresql.org Subject: Re: Can we remove support for standard_conforming_strings = off yet? Message-ID: References: <3279216.1767072538@sss.pgh.pa.us> <3730915.1767135010@sss.pgh.pa.us> <3924010.1767200681@sss.pgh.pa.us> <1706007.1768933913@sss.pgh.pa.us> <2402302.1769026170@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2402302.1769026170@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Jan 21, 2026 at 03:09:30PM -0500, Tom Lane wrote: > Julien Rouhaud 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 https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.