| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | 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:35:18 |
| Message-ID: | d06000f2-2acd-07a8-5ec6-874514f0763a@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Verite | 2017-06-15 13:35:24 | Re: Disallowing multiple queries per PQexec() |
| Previous Message | Amit Kapila | 2017-06-15 13:33:41 | Re: intermittent failures in Cygwin from select_parallel tests |