From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>, takaram71@gmail.com,
        pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17767: psql: tab-completion causes warnings when
 standard_conforming_strings = off
In-reply-to: <20230206143114.cpbkbtwkpmchyeco@alvherre.pgsql>
References: <20230206143114.cpbkbtwkpmchyeco@alvherre.pgsql>
Comments: In-reply-to Alvaro Herrera <alvherre@alvh.no-ip.org>
	message dated "Mon, 06 Feb 2023 15:31:14 +0100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2663395.1675696783.1@sss.pgh.pa.us>
Date: Mon, 06 Feb 2023 10:19:43 -0500
Message-ID: <2663396.1675696783@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/2663396.1675696783%40sss.pgh.pa.us>
Precedence: bulk

Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> Hmm, really?  We could just remove it for 16; people will still be able
> to use the warnings mode in 15 for several years, so if they want to
> upgrade to 16+ they will have plenty of time to update their apps.

I think removing standard_conforming_strings = off might be a
bridge too far, even yet.  Or were you speaking of removing
escape_string_warning?  I could get behind that perhaps.
Making it default to off could be an even easier sell.

			regards, tom lane