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

From Konstantin Knizhnik
Subject Re: Built-in connection pooling
Date
Msg-id dd458c56-5f06-95dd-c028-f1fac116e8b8@postgrespro.ru
Whole thread Raw
In response to Re: Built-in connection pooling  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Responses Re: Built-in connection pooling  (Nikolay Samokhvalov <samokhvalov@gmail.com>)
Re: Built-in connection pooling  (Vladimir Sitnikov <sitnikov.vladimir@gmail.com>)
List pgsql-hackers


On 06.04.2018 20:03, Konstantin Knizhnik wrote:


On 06.04.2018 20:00, Konstantin Knizhnik wrote:
Attached please find new version of the patch with  several bug fixes + support of more than one session pools associated with different ports.
Now it is possible to make postmaster listen several ports for accepting pooled connections, while leaving main Postgres port for dedicated backends.
Each session pool is intended to be used for particular database/user combination.

Sorry, wrong patch was attached.


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.
The last added feature is support of idle_in_transaction_session_timeout which is especially critical for builtin pool with transaction-level scheduling because long transaction can block other sessions executed at this backend.

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

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Boolean partitions syntax
Next
From: Michael Paquier
Date:
Subject: Re: wal_consistency_checking reports an inconsistency on masterbranch