Re: Built-in connection pooler
От | Zhihong Yu |
---|---|
Тема | Re: Built-in connection pooler |
Дата | |
Msg-id | CALNJ-vSnRHYi2q5S7pA39eXNccba0Qk9DhL2J9_C-j1TC5TE3Q@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Built-in connection pooler (Konstantin Knizhnik <knizhnik@garret.ru>) |
Ответы |
Re: Built-in connection pooler
Re: Built-in connection pooler |
Список | pgsql-hackers |
Hi,
+ With <literal>load-balancing</literal> policy postmaster choose proxy with lowest load average.
+ Load average of proxy is estimated by number of clients connection assigned to this proxy with extra weight for SSL connections.
+ Load average of proxy is estimated by number of clients connection assigned to this proxy with extra weight for SSL connections.
I think 'load-balanced' may be better than 'load-balancing'.
postmaster choose proxy -> postmaster chooses proxy
+ Load average of proxy is estimated by number of clients connection assigned to this proxy with extra weight for SSL connections.
I wonder if there would be a mixture of connections with and without SSL.
+ Terminate an idle connection pool worker after the specified number of milliseconds.
Should the time unit be seconds ? It seems a worker would exist for at least a second.
+ * Portions Copyright (c) 1996-2018, PostgreSQL Global Development Group
It would be better to update the year in the header.
+ * Use then for launching pooler worker backends and report error
Not sure I understand the above sentence. Did you mean 'them' instead of 'then' ?
Cheers
On Sun, Mar 21, 2021 at 11:32 AM Konstantin Knizhnik <knizhnik@garret.ru> wrote:
People asked me to resubmit built-in connection pooler patch to commitfest.
Rebased version of connection pooler is attached.
В списке pgsql-hackers по дате отправления: