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?
> 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.
I should think that in such cases, the end client is exactly not what
you want to be choosing which server it gets redirected to. You'd
be wanting to base that on policies defined at the pooler. There are
already plenty of client-supplied attributes you could use as inputs
for such policies (user name and application name, for instance).
Why do we need to incur a protocol break to add another one?
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
