Re: Built-in connection pooling

From: Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Built-in connection pooling
Date: 2018-01-19 09:52:51
Message-ID: be5978ba-445f-abb3-ee5e-5272bcd2a968@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 18.01.2018 18:02, Tomas Vondra wrote:
> Hi Konstantin,
>
> On 01/18/2018 03:48 PM, Konstantin Knizhnik wrote:
>> On 17.01.2018 19:09, Konstantin Knizhnik wrote:
>>> Hi hackers,
>>>
>>> ...
> I haven't looked at the code yet, but after reading your message I have
> a simple question - gow iss this going to work with SSL? If you're only
> passing a file descriptor, that does not seem to be sufficient for the
> backends to do crypto (that requires the SSL stuff from Port).
>
> Maybe I'm missing something and it already works, though ...
>
>
> regards
>
Ooops, I missed this aspect with SSL. Thank you.
New version of the patch which correctly maintain session context is
attached.
Now each session has its own allocator which should be  used instead of
TopMemoryAllocator.
SSL connections work now.

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

Attachment Content-Type Size
session_pool-3.patch text/x-patch 30.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yoshimi Ichiyanagi 2018-01-19 09:56:26 Re: [HACKERS][PATCH] Applying PMDK to WAL operations for persistent memory
Previous Message Amit Khandekar 2018-01-19 09:50:23 Re: [HACKERS] Useless code in ExecInitModifyTable