Re: PATCH: psql tab completion for SELECT - Mailing list pgsql-hackers

From David G. Johnston
Subject Re: PATCH: psql tab completion for SELECT
Date
Msg-id CAKFQuwafBrOnyOZgB1eJvTfRBjZQcwrXjNdL1vyxsiuB5CvM-A@mail.gmail.com
Whole thread Raw
In response to Re: PATCH: psql tab completion for SELECT  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: PATCH: psql tab completion for SELECT  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Mar 5, 2018 at 7:41 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
What would be actually useful is to be able to tab-complete even in
the midst of a failed transaction block ... but savepoints as such
won't get us there, and I have no good ideas about what would.

​Why not have psql open two sessions to the backend, one with application_name 'psql_user' and one with application name "psql_​meta" (or some such) and have all these queries executed on the psql_meta connection?

David J.

pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] Lazy hash table for XidInMVCCSnapshot (helps Zipfian a bit)
Next
From: David Steele
Date:
Subject: Re: 2018-03 CFM