From: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "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 21:59:23 |
Message-ID: | CAFCRh-9D37RTFNAFm-r+trq63kpk_M4cWGQ5_oG0hM+9QHLe7Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, May 18, 2022 at 5:43 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Wed, May 18, 2022 at 3:08 AM Dominique Devienne <ddevienne(at)gmail(dot)com>
> wrote:
>
>> Once connected, can I find out all aspects of the connection string?
>> Or where they came from, like a pgpass.conf or service file?
>>
>> How to get the host, port, db name once connected?
>> SHOW and pg_settings does not appear to be it, at first glance.
>>
>>
> The server has no clue how the values sent to it came into existence - nor
> should it.
>
> Whether and how any particular client might expose this kind of debugging
> information (or upgrade it to proper state info) is up to the client. I do
> not know what options psql offers.
>
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.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2022-05-18 22:37:55 | Re: Who am I? Where am I connected? |
Previous Message | David G. Johnston | 2022-05-18 21:18:16 | Re: Reasons for not overwriting processed wal archives? |