Request a Demo
Home   >   mailing lists

Re: Built-in connection pooling - Mailing list pgsql-hackers

From Nikolay Samokhvalov
Subject Re: Built-in connection pooling
Date
Msg-id CANNMO+K_FzaetEM4LLV4YnEnwjECc71etsPMYLAbOXQLmQtuGw@mail.gmail.com
Whole thread Raw
In response to Re: Built-in connection pooling  (Konstantin Knizhnik <[email protected]>)
Responses Re: Built-in connection pooling
List pgsql-hackers
Tree view
Understood.

One more question. Have you considered creation of pooling tool as a separate, not built-in tool, but being shipped with Postgres — like psql is shipped in packages usually called “postgresql-client-XX” which makes psql the default tool to work in terminal? I constantly hear opinion from various users, that Postgres needs “default”/official pooling tool.

вт, 17 апр. 2018 г. в 0:44, Konstantin Knizhnik <[email protected]>:


On 13.04.2018 19:07, Nikolay Samokhvalov wrote:
On Fri, Apr 13, 2018 at 2:59 AM, Konstantin Knizhnik <[email protected]> wrote:
Development in built-in connection pooling will be continued in  https://github.com/postgrespro/postgresql.builtin_pool.git
I am not going to send new patches to hackers mailing list any more.

Why? 

Just do not want to spam hackers with a lot of patches.
Also since I received few feedbacks in this thread, I consider that this topic is not so interesting for community.

Please notice that built-in connection pool is conn_pool branch.


-- 
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: pgindent run soon?
Next
From: John Naylor
Date:
Subject: Re: WIP: a way forward on bootstrap data