Hi
>From: Konstantin Knizhnik [mailto:k.knizh...@postgrespro.ru]
>>> From: Konstantin Knizhnik [mailto:k.knizh...@postgrespro.ru]
>>>
>>> New version of builtin connection pooler fixing handling messages of
>>> extended protocol.
>>>
>> 2. When proxy_port is a bit large (perhaps more than 2^15),
Hi.
>From: Konstantin Knizhnik [mailto:k.knizh...@postgrespro.ru]
>
>New version of builtin connection pooler fixing handling messages of extended
>protocol.
>
Here are things I've noticed.
1. Is adding guc to postgresql.conf.sample useful for users?
2. When proxy_port is a bit large (perhaps
>From: Konstantin Knizhnik [mailto:k.knizh...@postgrespro.ru]
>If the assumption that working set of backend (set of tables accessed by this
>session)
>is small enough to fit in backend's memory is true, then global meta cache is
>not
>needed at all: it is enough to limit size of local cache and
>>ShmZoneContext for SharedPlan and SharedRelCache is not implemented but
>>I'm going to do it following your points.
>
>After looking into existing code, I'm thinking Generation Memory Context seems
>to
>have the similar purpose. So I'll implement ShmZoneContext by reference it.
>Generation
Hi,
>ShmZoneContext for SharedPlan and SharedRelCache is not implemented but I'm
>going to do it following your points.
After looking into existing code, I'm thinking Generation Memory Context
seems to have the similar purpose. So I'll implement ShmZoneContext
by reference it.
Generation
Hi,
Sorry for waiting.
>Thomas Munro wrote:
>>What do you think about the following? Even though I know you want to
>>start with much simpler kinds of cache, I'm looking ahead to the lofty
>>end-goal of having a shared plan cache. No doubt, that involves
>>solving many other problems that
Hi, Konstantin
>>From: Konstantin Knizhnik [mailto:k.knizh...@postgrespro.ru]
>>I do not completely understand from your description when are are going
>>to evict entry from local cache?
>>Just once transaction is committed? I think it will be more efficient
>>to also specify memory threshold for
Hi, Alvaro
>
>The last patch we got here (a prototype) was almost a year ago. There was
>substantial discussion about it, but no new version of the patch has been
>posted. Are
>we getting a proper patch soon, or did we give up on the approach entirely?
I'm sorry for the late response. I
Hi, Konstantin
I'm very sorry for the late response and thank you for your feedback.
(I re-sent this email because my email address changed and couldn't deliver to
hackers.)
>From: Konstantin Knizhnik [mailto:k.knizh...@postgrespro.ru]
>
>Takeshi-san,
>
>I am sorry for late response - I just
