Re: [HACKERS] Making server name part of the startup message - Mailing list pgsql-hackers

From Satyanarayana Narlapuram
Subject Re: [HACKERS] Making server name part of the startup message
Date
Msg-id DM2PR03MB4167FF1487DC9A970A175B491C70@DM2PR03MB416.namprd03.prod.outlook.com
Whole thread Raw
In response to Re: [HACKERS] Making server name part of the startup message  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers

-----Original Message-----
From: Andres Freund [mailto:andres@anarazel.de]
Sent: Friday, June 16, 2017 10:48 AM
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Satyanarayana Narlapuram <Satyanarayana.Narlapuram@microsoft.com>; pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] Making server name part of the startup message

On 2017-06-15 09:43:13 -0400, Tom Lane wrote:
> Satyanarayana Narlapuram <Satyanarayana.Narlapuram@microsoft.com> writes:
> > As a cloud service, Azure Database for PostgreSQL uses a gateway proxy to route connections to a node hosting the
actualserver. To do that, the proxy needs to know the name of the server it tries to locate. As a work-around we
currentlyoverload the username parameter to pass in the server name using username@servername convention. It is purely
aconvention that our customers need to follow and understand. We would like to extend the PgSQL connection protocol to
addan optional parameter for the server name to help with this scenario. 
>
> We don't actually have any concept of a server name at the moment, and
> it isn't very clear what introducing that concept would buy.
> Please explain.

cluster_name could be what's meant?

Andres, thank you! It is database cluster name as you mentioned.

- Andres



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Preliminary results for proposed new pgindent implementation
Next
From: narlapurams
Date:
Subject: Re: [HACKERS] Making server name part of the startup message