| From: | vignesh C <vignesh21(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Jelte Fennema <postgres(at)jeltef(dot)nl>, 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>, 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: | 2024-01-08 05:08:00 |
| Message-ID: | CALDaNm3gsbS9BHuc70+XHZshDOWX0ZjXjY45qKFMTL31COLGuw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 12 Sept 2023 at 14:39, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> On 11.09.23 13:59, Jelte Fennema wrote:
> > @Tom and @Robert, since you originally suggested extending the
> > protocol for this, I think some input from you on the protocol design
> > would be quite helpful. BTW, this protocol extension is the main
> > reason I personally care for this patch, because it would allow
> > PgBouncer to ask for updates on certain GUCs so that it can preserve
> > session level SET commands even in transaction pooling mode.
> > Right now PgBouncer can only do this for a handful of GUCs, but
> > there's quite a few others that are useful for PgBouncer to preserve
> > by default:
> > - search_path
> > - statement_timeout
> > - lock_timeout
>
> ISTM that for a purpose like pgbouncer, it would be simpler to add a new
> GUC "report these variables" and send that in the startup message? That
> might not help with the psql use case, but it would be much simpler.
I have changed the status to "Waiting on Author" as Peter's comments
have not been followed up yet.
Regards,
Vignesh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2024-01-08 05:23:17 | Re: introduce dynamic shared memory registry |
| Previous Message | vignesh C | 2024-01-08 04:55:34 | Re: Forbid the use of invalidated physical slots in streaming replication. |