Re: Built-in connection pooler
| От | Michael Paquier |
|---|---|
| Тема | Re: Built-in connection pooler |
| Дата | |
| Msg-id | 20190129051403.GF3121@paquier.xyz обсуждение исходный текст |
| Ответ на | Re: Built-in connection pooler (Dimitri Fontaine <dimitri@citusdata.com>) |
| Ответы |
Re: Built-in connection pooler
|
| Список | pgsql-hackers |
On Mon, Jan 28, 2019 at 10:33:06PM +0100, Dimitri Fontaine wrote: > In other cases, it's important to measure and accept the possible > performance cost of running a proxy server between the client connection > and the PostgreSQL backend process. I believe the numbers shown in the > previous email by Konstantin are about showing the kind of impact you > can see when using the patch in a use-case where it's not meant to be > helping much, if at all. Have you looked at the possibility of having the proxy worker be spawned as a background worker? I think that we should avoid spawning any new processes on the backend from the ground as we have a lot more infrastructures since 9.3. The patch should actually be bigger, the code is very raw and lacks comments in a lot of areas where the logic is not so obvious, except perhaps to the patch author. -- Michael
Вложения
В списке pgsql-hackers по дате отправления: