| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | knizhnik(at)garret(dot)ru |
| 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 07:55:12 |
| Message-ID: | 20230613.165512.2091685398843624399.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Tue, 13 Jun 2023 09:55:36 +0300, Konstantin Knizhnik <knizhnik(at)garret(dot)ru> wrote in
> Postgres backend is "thick" not because of large number of local
> variables.
> It is because of local caches: catalog cache, relation cache, prepared
> statements cache,...
> If they are not rewritten, then backend still may consume a lot of
> memory even if it will be thread rather then process.
> But threads simplify development of global caches, although it can be
> done with DSM.
With the process model, that local stuff are flushed out upon
reconnection. If we switch to the thread model, we will need an
expiration mechanism for those stuff.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Naylor | 2023-06-13 08:19:47 | Re: Doc limitation update proposal: include out-of-line OID usage per TOAST-ed columns |
| Previous Message | Michael Paquier | 2023-06-13 07:50:54 | Re: Support logical replication of DDLs |