On Wed, Jun 21, 2017 at 12:15 PM, Robert Haas wrote:
> I think the problem is real,
> but I'm not sure that this is the best solution. On the other hand,
> I'm also not entirely sure I understand the proposal yet.
Given the problems with changing the protocol it does seem like
generalizing away
On Thu, Jun 15, 2017 at 9:50 AM, Tom Lane wrote:
> Can you give a concrete example where this would have
> helped above and beyond knowing, eg, the source and time of the connection
> attempt?
I can imagine that in really high-volume use cases (such as the OP
apparently has) the number of client
On Thu, Jun 15, 2017 at 3:11 AM, Satyanarayana Narlapuram
wrote:
> The proposal is to tweak the connectivity wire protocol, and add a
> connection id (GUID) filed in the startup message. We can trace the
> connection using this GUID and investigate further on where the connection
> failed.
Wire p
Satyanarayana Narlapuram writes:
> As a cloud service, Azure Database for PostgreSQL uses a gateway proxy to
> route connections to a node hosting the actual server. Potentially there
> could be multiple hops (for example client, optional proxy at the client like
> pgbouncer for connection pool
* Peter Eisentraut (peter.eisentr...@2ndquadrant.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 t
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
As a cloud service, Azure Database for PostgreSQL uses a gateway proxy to route
connections to a node hosting the actual server. Potentially there could be
multiple hops (for example client, optional proxy at the client like pgbouncer
for connection pooling, Azure gateway proxy, backend server)