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

From Thom Brown
Subject Re: Changing shared_buffers without restart
Date
Msg-id CAA-aLv7p=9jCy_-67+Wj2vrRL1QCV-X0ZFZmpAxBJqLPp-ho+A@mail.gmail.com
Whole thread Raw
In response to Re: Changing shared_buffers without restart  (Dmitry Dolgov <9erthalion6@gmail.com>)
Responses Re: Changing shared_buffers without restart
List pgsql-hackers
On Mon, 14 Jul 2025, 09:54 Dmitry Dolgov, <9erthalion6@gmail.com> wrote:
> On Mon, Jul 14, 2025 at 01:55:39PM +0530, Ashutosh Bapat wrote:
> > You're right of course, a buffer id could be returned from the
> > ClockSweep and from the custom strategy buffer ring. Buf from what I see
> > those are picking a buffer from the set of already utilized buffers,
> > meaning that for a buffer to land there it first has to go through
> > StrategyControl->firstFreeBuffer, and hence the idea above will be a
> > requirement for those as well.
>
> That isn't true. A buffer which was never in the free list can still
> be picked up by clock sweep.

How's that?

Isn't it its job to find usable buffers from the used buffer list when no free ones are available? The next victim buffer can be selected (and cleaned if dirty) and then immediately used without touching the free list.

Thom


pgsql-hackers by date:

Previous
From: Japin Li
Date:
Subject: Re: Requested WAL segment xxx has already been removed
Next
From: Dmitry Dolgov
Date:
Subject: Re: Changing shared_buffers without restart