| From: | Andreas Karlsson <andreas(at)proxel(dot)se> |
|---|---|
| To: | Konstantin Knizhnik <knizhnik(at)garret(dot)ru>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | pashkin(dot)elfe(at)gmail(dot)com, dilipbalaut(at)gmail(dot)com, hannuk(at)google(dot)com, hlinnaka(at)iki(dot)fi, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Let's make PostgreSQL multi-threaded |
| Date: | 2023-06-13 10:05:48 |
| Message-ID: | 40b563bb-f4f1-9255-3c66-44c4fbcfd07f@proxel.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hayato Kuroda (Fujitsu) | 2023-06-13 10:05:56 | RE: [PATCH] Reuse Workers and Replication Slots during Logical Replication |
| Previous Message | Amit Langote | 2023-06-13 09:38:42 | Re: Views no longer in rangeTabls? |