| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Satyanarayana Narlapuram <Satyanarayana(dot)Narlapuram(at)microsoft(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Adding connection id in the startup message |
| Date: | 2017-06-15 13:38:37 |
| Message-ID: | 20170615133837.GR1769@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Peter Eisentraut (peter(dot)eisentraut(at)2ndquadrant(dot)com) wrote:
> On 6/15/17 03:11, Satyanarayana Narlapuram wrote:
> > Client adds a connection id in the startup message and send it to the
> > server it is trying to connect to. Proxy logs the connection id
> > information in its logs, and passes it to the server. Server logs the
> > connection Id in the server log, and set it in the GUC variable
> > (ConnectionId).
>
> If you're using pgbouncer or similar, then it might reuse an already
> existing connection, so your connection ID wouldn't be passed on.
This tends to be what people (as pgbouncer does) use application_name
for.
Thanks!
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-06-15 13:43:13 | Re: Making server name part of the startup message |
| Previous Message | Daniel Verite | 2017-06-15 13:35:24 | Re: Disallowing multiple queries per PQexec() |