| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Who am I? Where am I connected? |
| Date: | 2022-05-18 23:12:47 |
| Message-ID: | 63571.1652915567@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dominique Devienne <ddevienne(at)gmail(dot)com> writes:
> AFAIK, it’s not psql that does this though, it’s libpq the official client
> api.
> And the fact libpq has no way to surface that info seems like an important
> oversight.
PQconninfo() will show you all the option values in use by a connection
object. It's true that it's not very easy to tell where any given value
came from, but I doubt it'd be worth an ABI break to add such info.
(You could at least recognize values that match the hard-wired default
or environment variable value.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | 菊池祐 | 2022-05-19 04:18:35 | About pg_basebackup |
| Previous Message | itman73 | 2022-05-18 22:40:44 | switchover and switchback assistance ... |