Request a Demo
Home   >   mailing lists

Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock
Date
Msg-id CA+TgmoYw2psUKOA0egV20_emsHBbFCpa9egvkSE6fPYAj126_Q@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Let's get rid of the freelist and the buffer_strategy_lock  ("Greg Burd" <greg@burd.me>)
List pgsql-hackers
Tree view 
On Fri, Jul 11, 2025 at 3:48 PM Greg Burd <greg@burd.me> wrote:
> I briefly considered how one might use what was left after surgery to produce some similar boolean signal to no
avail. I think that autoprewarm was simply trying to at most warm NBuffers then stop.  The freelist at startup was just
aconvenient thing to drain and get that done.  Maybe I'll try adapting autoprewarm to consider that global instead. 

My concern had been that while autoprewarm was running, other system
activity could already have started and been filling up
shared_buffers. By considering whether there were actually free
buffers remaining, it would prewarm less in that case.

I'm not saying that was the perfect idea, I'm just telling you what I
was thinking at the time.

--
Robert Haas
EDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Ashutosh Sharma
Date:
Subject: Re: Improve pg_sync_replication_slots() to wait for primary to advance
Next
From: Nathan Bossart
Date:
Subject: Re: [PATCH] Add tests for Bitmapset