Feedback-ID: ia2694551:Fastmail
Date: Mon, 6 Feb 2023 15:31:14 +0100
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: tgl@sss.pgh.pa.us, takaram71@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17767: psql: tab-completion causes warnings when
 standard_conforming_strings = off
Message-ID: <20230206143114.cpbkbtwkpmchyeco@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20230202.173840.514794946954779039.horikyota.ntt@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/20230206143114.cpbkbtwkpmchyeco%40alvherre.pgsql>
Precedence: bulk

On 2023-Feb-02, Kyotaro Horiguchi wrote:

> > Now, I don't foresee that actually happening any time soon (and every
> > report of somebody still using standard_conforming_strings = off
> > pushes out my idea of when it could happen).  But perhaps allowing
> > minor annoyances like this to go unfixed would start to light a
> > fire under people to get off of that setting.
> 
> That seems like the right decision for to-be-obsolete features.  Or,
> we can explicitly mar that variables as OBSOLETE then rip off it a few
> years later.

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.

If we decide to keep it, then ISTM we should find a way to make this tab
completion thingy work silently.  But I'd rather we didn't spend any
time on it.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/
"Porque Kim no hacía nada, pero, eso sí,
con extraordinario éxito" ("Kim", Kipling)