From: | 'Alvaro Herrera' <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
Cc: | "'pgsql-hackers(at)lists(dot)postgresql(dot)org'" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Some shared memory chunks are allocated even if related processes won't start |
Date: | 2024-03-04 11:52:47 |
Message-ID: | 202403041152.fl4psozsstnt@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2024-Mar-04, Hayato Kuroda (Fujitsu) wrote:
> However, the second idea is still valid, which allows the allocation
> of shared memory dynamically. This is a bit efficient for the system
> which tuples won't be frozen. Thought?
I think it would be worth allocating AutoVacuumShmem->av_workItems using
dynamic shmem allocation, particularly to prevent workitems from being
discarded just because the array is full¹; but other than that, the
struct is just 64 bytes long so I doubt it's useful to allocate it
dynamically.
¹ I mean, if the array is full, just allocate another array, point to it
from the original one, and keep going.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"The problem with the facetime model is not just that it's demoralizing, but
that the people pretending to work interrupt the ones actually working."
-- Paul Graham, http://www.paulgraham.com/opensource.html
From | Date | Subject | |
---|---|---|---|
Next Message | Mats Kindahl | 2024-03-04 11:59:46 | Hooking into ExplainOneQuery() complicated by missing standard_ExplainOneQuery |
Previous Message | Andrey M. Borodin | 2024-03-04 11:51:46 | Re: CF entries for 17 to be reviewed |