| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Cc: | Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> |
| Subject: | Re: Let's make PostgreSQL multi-threaded |
| Date: | 2023-06-05 17:32:34 |
| Message-ID: | CAHyXU0zAsbB1FsN=RBp3sk=n9FpcU5YN7gFKNG41QPWQAtP9Mg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 5, 2023 at 12:25 PM Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> We currently bend over backwards to make all allocations fixed-sized in
> shared memory. You learn to live with that, but a lot of things would be
> simpler if you could allocate and free in shared memory more freely.
> It's no panacea, you still need to be careful with locking and
> concurrency. But a lot simpler.
Would this help with oom killer in linux?
Isn't it true that pgbouncer provides a lot of the same benefits?
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2023-06-05 17:40:13 | Re: Let's make PostgreSQL multi-threaded |
| Previous Message | Heikki Linnakangas | 2023-06-05 17:29:16 | Re: Let's make PostgreSQL multi-threaded |