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 1viVVb-008Gat-1n for pgsql-hackers@arkaria.postgresql.org; Wed, 21 Jan 2026 10:32:20 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1viVVa-006Vcf-26 for pgsql-hackers@arkaria.postgresql.org; Wed, 21 Jan 2026 10:32:18 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1viVVa-006VcW-18 for pgsql-hackers@lists.postgresql.org; Wed, 21 Jan 2026 10:32:18 +0000 Received: from mail-pl1-x62b.google.com ([2607:f8b0:4864:20::62b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1viVVY-001ZoJ-16 for pgsql-hackers@lists.postgresql.org; Wed, 21 Jan 2026 10:32:17 +0000 Received: by mail-pl1-x62b.google.com with SMTP id d9443c01a7336-2a102494058so4156075ad.0 for ; Wed, 21 Jan 2026 02:32:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1768991536; x=1769596336; darn=lists.postgresql.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=uoL430qLy4QGoEnHrUV+XH3pE7d6jpWL8hK5HyBXtuU=; b=PhX7uqT6AT6LQ9G+rsZ48MnOAPJfSxv3RVCJnpRdNbr3MuUuTnq7odR+pDbDZX+nZI ymE3DhL0xb3IbOzGR/lEgGBGjyYhG7jbCsabnADcsqrjmLiU+U1ArapwDUyumAM6qRMA 8qxFqymEP3p0jkbSXbsClTO8cOH2mYX2U62CkzcMp/GBR3PWLamJnkEW8emUEJgb+PXF giB3G6CnR9JFOE7rysZ6DW5wC3iZmFTL4noyGL1tbqNNSmWwNihkARcGAymto3YwApia Mgqro4Ev0bZhdrsNXH73JBa8wrFQ6W1l7N4pfahaC+/PPmkdq95UxZfaBiBgxAQtqipi ijSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1768991536; x=1769596336; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=uoL430qLy4QGoEnHrUV+XH3pE7d6jpWL8hK5HyBXtuU=; b=GpjFr5qZ79dpLBBIlT+nN3LUIxp5xObAzjwQBuwuNOVYSy+XQuorJyUz3oOaN9AaRp fGhSqPGAX6KD75gHP8Wmh7qultbx4p8pnVbBcyWmbet9Xpeqp0KO/naBpcNAcvutBxPn uujW5ga0cY5AvtaX+8rZlvVt8mZRJpr+xNxkU8t4HEpjl1QpquyDwmDcHJFNprQeqsRF 74ubd0uhTsRSQNh5Ewt9xZnxkUEhDUiPIE8+rhFBWfd/P+bwn4hqWj8KHtHKP9Ia52ns MwYRrUAjyG3dQs48NJ1M9w0iCVWrtXk5UvGqCBvqfbVwNi5aAFWL7AW/zoHsIcNrXwL4 oZvA== X-Forwarded-Encrypted: i=1; AJvYcCUnZ2lgJEnMmBo3oGAzEzolzbXzRjP96jBQUljHktSQPj7zMCBtFwaw39T/CcP4Zp2FtufaCN/wJoXtjgc7@lists.postgresql.org X-Gm-Message-State: AOJu0Yx4heqOyeVjwmzlp6yh5s4uFiBJ510hswnodmqZC23Us1HSgUkB wEbnhD62T6U0fgY+lCzuft7flTZArzTzOKphSFvuWyu7VcNZbsX1w2pC X-Gm-Gg: AZuq6aIYY4GISPTKO5U8scu2BXKNU0YxmWLmfz2c4u+/riFGDpRYaU3tgc7CDSHwIGD /N/vqtn0jfpp1eow0A7MhyQxqj7akHPf6kGaDmM+kGkN/QhYemOXlfSaC8yYPJceEXohwNfGDvr TVDYpZ0NqhphXXTX/pfs3HounrR9HjyB/909h49LrfjuuZpFwj+2N8wA/zMZeCyY+K6zZIWPfAp Pv0Lkl+GOQ3cLcDDAonorBI3YKRvSTCLsMMrM16SteTfQqkl5hoNPt/Wz6gv1bxSEeWdhw0e8XT YOxBWVX6B033Eyxu3/9iWTH12BkGichMbQ0xtOqiqzD3AS1RWtFsu1MRx/GyMJWdaQVL6zTE8+X yeh6LmZ/35K6wjiHKZOQc3KA7hm3MG7jkNRPFxU8vgpHiwix2PxUFJGDHBCW615iCwqaqtPZUOV s4uii6QK8AB0o4JQ== X-Received: by 2002:a17:902:d2c2:b0:2a0:906b:db3e with SMTP id d9443c01a7336-2a700a51fecmr196864505ad.27.1768991535978; Wed, 21 Jan 2026 02:32:15 -0800 (PST) Received: from jrouhaud ([115.43.41.38]) by smtp.gmail.com with ESMTPSA id d9443c01a7336-2a751b94562sm50796995ad.53.2026.01.21.02.32.14 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 21 Jan 2026 02:32:15 -0800 (PST) Date: Wed, 21 Jan 2026 18:32:11 +0800 From: Julien Rouhaud To: Tom Lane Cc: 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1706007.1768933913@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, 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.