Re: [HACKERS] Making server name part of the startup message
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] Making server name part of the startup message |
Дата | |
Msg-id | 9838.1497542260@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] Making server name part of the startup message (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Ответы |
Re: [HACKERS] Making server name part of the startup message
Re: [HACKERS] Making server name part of the startup message |
Список | pgsql-hackers |
Alvaro Herrera <alvherre@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
В списке pgsql-hackers по дате отправления: