Re: [HACKERS] Making server name part of the startup message

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

Re: [HACKERS] Making server name part of the startup message

arayana Narlapuram <satyanarayana.narlapu...@microsoft.com>; pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Making server name part of the startup message On Thu, Jun 15, 2017 at 5:57 PM, Tom Lane <t...@sss.pgh.pa.us<mailto:t...@sss.pgh.pa.us>> wrote: Alvaro Herrera &l

Re: [HACKERS] Making server name part of the startup message

pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Making server name part of the startup message Alvaro Herrera <alvhe...@2ndquadrant.com> writes: > Tom Lane wrote: >> This makes no sense at all. The client is telling the server what >> the server's name is? >

Re: [HACKERS] Making server name part of the startup message

-Original Message- From: Andres Freund [mailto:and...@anarazel.de] Sent: Friday, June 16, 2017 10:48 AM To: Tom Lane <t...@sss.pgh.pa.us> Cc: Satyanarayana Narlapuram <satyanarayana.narlapu...@microsoft.com>; pgsql-hackers@postgresql.org Subject: Re: [HACKERS] Making serv

Re: [HACKERS] Making server name part of the startup message

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

Re: [HACKERS] Making server name part of the startup message

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

Re: [HACKERS] Making server name part of the startup message

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

Re: [HACKERS] Making server name part of the startup message

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

Re: [HACKERS] Making server name part of the startup message

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

Re: [HACKERS] Making server name part of the startup message

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

Re: [HACKERS] Making server name part of the startup message

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

[HACKERS] Making server name part of the startup message

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