Horton

Re: Add pg_buffercache_evict_all() and pg_buffercache_mark_dirty[_all]() functions

Bertrand Drouvot <bertranddrouvot.pg@gmail.com>

View thread View on postgr.es
From: Bertrand Drouvot <bertranddrouvot.pg@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: Nazir Bilal Yavuz <byavuz81@gmail.com>, Aidar Imamov <a.imamov@postgrespro.ru>, Joseph Koshakow <koshy44@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-04-10T13:50:36Z
Lists: pgsql-hackers 
Hi,

On Tue, Apr 08, 2025 at 02:40:52AM -0400, Andres Freund wrote:
> I think it's ok for now.  It might be worth doing a larger redesign of the
> pgbuffercache docs at some point...
> 
> 
> Pushed.
> 
> 
> Thanks for your patches and thanks for all the reviewers getting this ready!

Thanks for the patch! That sounds like a great addition. I was doing some
tests and did not see any issues. Also while doing the tests I thouhgt that it
could be useful to evict only from a subset of NUMA nodes (now that NUMA
awareness is in). We'd need to figure out what to do for buffers that are spread
across NUMA nodes though.

Does that sound like an idea worth to spend time on? (If so, I'd be happy to work
on it).

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

Commits

  1. pg_buffercache: Add pg_buffercache_mark_dirty{,_relation,_all}()

  2. doc: Add missing tags in pg_buffercache page

  3. Add routines for marking buffers dirty efficiently

  4. Add pg_buffercache_evict_{relation,all} functions