From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nathan Bossart <nathandbossart@gmail.com>
cc: pgsql-hackers@postgresql.org
Subject: Re: remove VersionedQuery support from psql tab completion
In-reply-to: <akazLuA2V2_auKiN@nathan>
References: <akazLuA2V2_auKiN@nathan>
Comments: In-reply-to Nathan Bossart <nathandbossart@gmail.com>
	message dated "Thu, 02 Jul 2026 13:51:26 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <3790464.1783030658.1@sss.pgh.pa.us>
Date: Thu, 02 Jul 2026 18:17:38 -0400
Message-ID: <3790465.1783030658@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/3790465.1783030658%40sss.pgh.pa.us>
Precedence: bulk

Nathan Bossart <nathandbossart@gmail.com> writes:
> This infrastructure was added by commit 722408bcd1 and was only ever used
> for publications and subscriptions.  Since we just bumped psql's minimum
> supported version to v10, it's no longer used by anything.  Furthermore, a
> quick glance indicates there's nothing else that should use it.  So, IMHO
> we might as well remove it.

This seems a little short-sighted.  Do you think we'll never again
make any catalog changes that affect tab completion?  Admittedly,
maybe all such cases will fall under what SchemaQuery is good for.
But that's significantly harder to use, so I'm not really in a
hurry to make that tradeoff.

			regards, tom lane