Satyanarayana Narlapuram writes:
>> Why do we need to incur a protocol break to add another one?
> This is optional and is not a protocol break.
Yes, it is. We've been around on this sort of thing before and we
understand the consequences. If the option is carried in the startup
message, the c
ACKERS] Making server name part of the startup message
On Thu, Jun 15, 2017 at 5:57 PM, Tom Lane
mailto:t...@sss.pgh.pa.us>> wrote:
Alvaro Herrera mailto:alvhe...@2ndquadrant.com>>
writes:
> Tom Lane wrote:
>> This makes no sense at all. The client is telling the server what th
_name in the startup message and will not be included otherwise.
Thanks,
Satya
-Original Message-
From: Tom Lane [mailto:t...@sss.pgh.pa.us]
Sent: Thursday, June 15, 2017 8:58 AM
To: Alvaro Herrera
Cc: Satyanarayana Narlapuram ;
pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Ma
-Original Message-
From: Andres Freund [mailto:and...@anarazel.de]
Sent: Friday, June 16, 2017 10:48 AM
To: Tom Lane
Cc: Satyanarayana Narlapuram ;
pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Making server name part of the startup message
On 2017-06-15 09:43:13 -0400, Tom
Thank you, Alvaro, Andres, Magnus, Peter, and Tom for your thoughts! I
consolidated all the responses, and provided the high level overview of the
Azure PostgreSQL database architecture, and provided additional details at
the bottom of the message.
> Tom Lane: We don't actually have any concept o
On 2017-06-15 09:43:13 -0400, Tom Lane wrote:
> 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. To do that, the
> > proxy needs to know the name of the server it tries to loc
On Thu, Jun 15, 2017 at 5:57 PM, Tom Lane wrote:
> Alvaro Herrera writes:
> > Tom Lane wrote:
> >> This makes no sense at all. The client is telling the server what the
> >> server's name is?
>
> > I think for instance you could have one pgbouncer instance (or whatever
> > pooler) pointing to s
Alvaro Herrera writes:
> Tom Lane wrote:
>> This makes no sense at all. The client is telling the server what the
>> server's name is?
> I think for instance you could have one pgbouncer instance (or whatever
> pooler) pointing to several different servers. So the client connects
> to the poole
Tom Lane wrote:
> Satyanarayana Narlapuram writes:
> > Change the Postgres wire protocol to include server name in the startup
> > message. This field can be an optional field driven by the connection
> > parameters for psql (-N, --servername).
> > We need this extra parameter for backward comp
On 6/15/17 03:20, Satyanarayana Narlapuram wrote:
> As a cloud service, Azure Database for PostgreSQL uses a gateway proxy
> to route connections to a node hosting the actual server. To do that,
> the proxy needs to know the name of the server it tries to locate. As a
> work-around we currently ove
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. To do that, the proxy
> needs to know the name of the server it tries to locate. As a work-around we
> currently overload the use
As a cloud service, Azure Database for PostgreSQL uses a gateway proxy to route
connections to a node hosting the actual server. To do that, the proxy needs to
know the name of the server it tries to locate. As a work-around we currently
overload the username parameter to pass in the server name
12 matches
Mail list logo
