Re: Let's make PostgreSQL multi-threaded - Mailing list pgsql-hackers

From Andreas Karlsson
Subject Re: Let's make PostgreSQL multi-threaded
Date
Msg-id 40b563bb-f4f1-9255-3c66-44c4fbcfd07f@proxel.se
Whole thread Raw
In response to Re: Let's make PostgreSQL multi-threaded  (Konstantin Knizhnik <knizhnik@garret.ru>)
List pgsql-hackers
On 6/13/23 10:20, Konstantin Knizhnik wrote:
> The fact that it is flushed out upon reconnection can not 
> help much: what if backends are not going to disconnect?

This is why many connection pools have a maximum connection lifetime 
which can be configured. So in practice flushing all caches on 
disconnect helps a lot.

The nice proper solution might very well be adding a maximum cache sizes 
and replacement but it obviously makes the cache more complex and adds 
an new GUC. Probably worth it, but flushing caches on disconnect is a 
simple solution which works well in practice for many but no all workloads.

Andreas




pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Views no longer in rangeTabls?
Next
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: [PATCH] Reuse Workers and Replication Slots during Logical Replication