Re: Built-in connection pooling

From: Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Built-in connection pooling
Date: 2018-04-13 09:59:05
Message-ID: dd458c56-5f06-95dd-c028-f1fac116e8b8@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2018-04-13 10:08:40 Re: wal_consistency_checking reports an inconsistency on master branch
Previous Message Amit Langote 2018-04-13 09:55:30 Re: Boolean partitions syntax