From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Satyanarayana Narlapuram <Satyanarayana(dot)Narlapuram(at)microsoft(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Making server name part of the startup message |
Date: | 2017-06-15 15:40:50 |
Message-ID: | 20170615154050.kzok7bmwe3mj3oth@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Satyanarayana Narlapuram <Satyanarayana(dot)Narlapuram(at)microsoft(dot)com> 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 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.
>
> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2017-06-15 15:49:48 | Re: Misnaming of staext_dependencies_load |
Previous Message | Peter Eisentraut | 2017-06-15 15:25:59 | Re: logical replication read-only slave |