From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
---|---|
To: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com> |
Cc: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com> |
Subject: | Re: Changing shared_buffers without restart |
Date: | 2025-10-01 10:42:38 |
Message-ID: | l6vgpjg5dcqmta5hag6b7s7b6qgmi3ln2atri2gn6ymvj5ncyk@qlbzgy7vqf25 |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On Wed, Oct 01, 2025 at 03:50:17PM +0530, Ashutosh Bapat wrote:
> The buffer lookup table itself.
> /* Pass location of hashtable header to hash_create */
> infoP->hctl = (HASHHDR *) location;
How does this affect any users of the lookup table, if they do not even
get to see those?
> > Shared buffer lookup table already lives in it's own segment as
> > implemented in the current patch, so I don't see any problem here.
>
> The table is not a single chunk of memory. It's a few chunks spread
> across the shared memory segment. Freeing a lookup table is like
> freeing those chunks. We have ways to free tail parts of shared memory
> segments, but not chunks in-between.
Right, and the idea was to rebuild it completely to fit into the new
size, not just chunk-by-chunk.
From | Date | Subject | |
---|---|---|---|
Next Message | Hayato Kuroda (Fujitsu) | 2025-10-01 11:00:54 | RE: POC: enable logical decoding when wal_level = 'replica' without a server restart |
Previous Message | Álvaro Herrera | 2025-10-01 10:37:20 | Re: pg_createsubscriber --dry-run logging concerns |