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

From Alvaro Herrera
Subject Re: [HACKERS] Making server name part of the startup message
Date
Msg-id 20170615154050.kzok7bmwe3mj3oth@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] Making server name part of the startup message  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Making server name part of the startup message  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Satyanarayana Narlapuram <Satyanarayana.Narlapuram@microsoft.com> writes:

> > Change the Postgres wire protocol to include server name in the startup message. This field can be an optional
fielddriven 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'tneed this field, this change helps making the server name by default included in the startup message in future.
 
> 
> 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 pooler and indicates which of the servers to connect to.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] logical replication read-only slave
Next
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Misnaming of staext_dependencies_load