Making server name part of the startup message

From: Satyanarayana Narlapuram <Satyanarayana(dot)Narlapuram(at)microsoft(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Making server name part of the startup message
Date: 2017-06-15 07:20:00
Message-ID: DM2PR03MB4168F3C796B2965FDC4CF9991C00@DM2PR03MB416.namprd03.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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 using username(at)servername convention. It is purely a convention that our customers need to follow and understand. We would like to extend the PgSQL connection protocol to add an optional parameter for the server name to help with this scenario.

Proposed changes:

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 compatibility.
Make PostgreSQL server aware of the new field, and accept the startup message containing this field. Though server doesn't need this field, this change helps making the server name by default included in the startup message in future.

P.S: I would like to get some initial feedback on this idea and will provide more design details if required. Any feedback in this regard is really appreciated.

Thanks,
Satya

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Shubham Barai 2017-06-15 07:48:13 Re: GSoC 2017 weekly progress reports (week 2)
Previous Message Satyanarayana Narlapuram 2017-06-15 07:11:04 Adding connection id in the startup message