| From: | Jelte Fennema <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Kirk Wolak <wolakk(at)gmail(dot)com>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: proposal: psql: show current user in prompt |
| Date: | 2023-09-11 12:03:22 |
| Message-ID: | CAGECzQQOm-zXip0q+Xcd6jcYhi98_wM=NKyKwFVPpBzCdKLbEg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 11 Sept 2023 at 13:59, Jelte Fennema <postgres(at)jeltef(dot)nl> wrote:
> I think that would make the client code even simpler than it is now.
To be clear, I'm not saying we should do this. There's benefits to
using a dedicated new message type too (e.g. clearer errors if a proxy
like pgbouncer does not understand it).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2023-09-11 12:04:22 | Re: Eliminate redundant tuple visibility check in vacuum |
| Previous Message | David Rowley | 2023-09-11 12:00:10 | Re: Speed up transaction completion faster after many relations are accessed in a transaction |