| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Edmund Horner <ejrh00(at)gmail(dot)com>, Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PATCH: psql tab completion for SELECT |
| Date: | 2018-03-05 14:47:37 |
| Message-ID: | CAKFQuwafBrOnyOZgB1eJvTfRBjZQcwrXjNdL1vyxsiuB5CvM-A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Mar 5, 2018 at 7:41 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Steele | 2018-03-05 14:48:17 | Re: 2018-03 CFM |
| Previous Message | Tomas Vondra | 2018-03-05 14:44:43 | Re: [HACKERS] Lazy hash table for XidInMVCCSnapshot (helps Zipfian a bit) |