From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nathan Bossart <nathandbossart@gmail.com>
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: <ajK85yBHh_RK7x4T@nathan>
References: 
 <CA+fm-RM8bG0G6SJDaMgWkKmtyf4QG=V5We1ViAG0tZ5PU67rLQ@mail.gmail.com>
 <ajK85yBHh_RK7x4T@nathan>
Comments: In-reply-to Nathan Bossart <nathandbossart@gmail.com>
	message dated "Wed, 17 Jun 2026 10:27:35 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1124571.1781710583.1@sss.pgh.pa.us>
Date: Wed, 17 Jun 2026 11:36:23 -0400
Message-ID: <1124572.1781710583@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1124572.1781710583%40sss.pgh.pa.us>
Precedence: bulk

Nathan Bossart <nathandbossart@gmail.com> writes:
> [RMT hat]
> On Mon, May 11, 2026 at 05:21:57PM -0500, Baji Shaik wrote:
>> Commit 45762084 [1] forced standard_conforming_strings to always be ON in
>> PostgreSQL 19. The release notes mention this change, but neither the
>> pg_dump/pg_restore reference pages nor the migration section note the
>> implications for restoring older dump files.

> There's an open item for this with Tom listed as the owner.  Tom, have you
> had a chance to take a look at this?

Oh, I didn't know this'd been assigned to me.  Will look.

			regards, tom lane