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 <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1waElX-001cuL-2g
	for pgsql-hackers@arkaria.postgresql.org;
	Thu, 18 Jun 2026 15:34:51 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.96)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1waElW-00CAib-2Q
	for pgsql-hackers@arkaria.postgresql.org;
	Thu, 18 Jun 2026 15:34:50 +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 <tgl@sss.pgh.pa.us>)
	id 1waElW-00CAiT-1Z
	for pgsql-hackers@lists.postgresql.org;
	Thu, 18 Jun 2026 15:34:50 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.98.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1waElV-00000000zdM-0R5r
	for pgsql-hackers@lists.postgresql.org;
	Thu, 18 Jun 2026 15:34:49 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 65IFYkTf1242906;
	Thu, 18 Jun 2026 11:34:46 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Bruce Momjian <bruce@momjian.us>
cc: Baji Shaik <baji.pgdev@gmail.com>, pgsql-hackers@lists.postgresql.org
Subject: Re: [PATCH] Doc: document standard_conforming_strings dump/restore
 incompatibility
In-reply-to: <ajMvEd0zXBMN-Bri@momjian.us>
References: 
 <CA+fm-RM8bG0G6SJDaMgWkKmtyf4QG=V5We1ViAG0tZ5PU67rLQ@mail.gmail.com>
 <1131492.1781717349@sss.pgh.pa.us> <ajMvEd0zXBMN-Bri@momjian.us>
Comments: In-reply-to Bruce Momjian <bruce@momjian.us>
	message dated "Wed, 17 Jun 2026 19:34:41 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1242904.1781796886.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 18 Jun 2026 11:34:46 -0400
Message-ID: <1242905.1781796886@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/1242905.1781796886%40sss.pgh.pa.us>
Precedence: bulk

Bruce Momjian <bruce@momjian.us> writes:
> On Wed, Jun 17, 2026 at 01:29:09PM -0400, Tom Lane wrote:
>> I'm inclined to do more or less the attached, which also fixes what
>> seems a thinko in the existing text: we should say that clients still
>> support standard_conforming_strings =3D off, not
>> escape_string_warning =3D off.

> I have applied a slightly modified version to master, attached.  The git
> commit suggested this problem, but I didn't understand the impact at the
> time I read it.

This didn't correct the point I complained of above: it still says

Client applications still support <literal>escape_string_warning =3D off</=
literal> for compatibility with old servers.

The notion of a client "supporting" escape_string_warning seems quite
meaningless.  I think this intended to say standard_conforming_strings =3D
off.

			regards, tom lane