Re: Changing shared_buffers without restart - Mailing list pgsql-hackers

From Dmitry Dolgov
Subject Re: Changing shared_buffers without restart
Date
Msg-id n5vpwbzdcml3fgsicixhhhy4p7syyudz5tam7wkyibnynih3iw@cbp53sufptga
Whole thread Raw
In response to Re: Changing shared_buffers without restart  ("Burd, Greg" <greg@burd.me>)
List pgsql-hackers
> On Mon, Jul 14, 2025 at 10:22:17AM -0400, Burd, Greg wrote:
> I'd initialize them, expand BufferDescriptors, and adjust NBuffers.  The
> clock-sweep algorithm will eventually find them and make use of them.  The
> buf->freeNext should be FREENEXT_NOT_IN_LIST so that StrategyFreeBuffer() will
> do the work required to append it the freelist after use.  AFAICT there is no
> need to add to the freelist up front.

Yep, thanks. I think this approach may lead to a problem I'm trying to
address with the buffer lookup table (just have described it in the
message above). But if I'm wrong, that of course would be the way to go.



pgsql-hackers by date:

Previous
From: Dmitry Dolgov
Date:
Subject: Re: Changing shared_buffers without restart
Next
From: Jack Ng
Date:
Subject: RE: Changing shared_buffers without restart