Re: Add pg_buffercache_mark_dirty[_all] functions to the pg_buffercache

Nazir Bilal Yavuz <byavuz81@gmail.com>

From: Nazir Bilal Yavuz <byavuz81@gmail.com>
To: Michael Paquier <michael@paquier.xyz>
Cc: Amit Kapila <amit.kapila16@gmail.com>, Xuneng Zhou <xunengzhou@gmail.com>, Andres Freund <andres@anarazel.de>, Aidar Imamov <a.imamov@postgrespro.ru>, Joseph Koshakow <koshy44@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-11-24T07:48:24Z
Lists: pgsql-hackers

Attachments

Hi,

On Mon, 24 Nov 2025 at 08:46, Michael Paquier <michael@paquier.xyz> wrote:
>
> On Fri, Aug 08, 2025 at 01:16:57PM +0300, Nazir Bilal Yavuz wrote:
> > Thank you for looking into this! And sorry for the late reply.
>
> Could you rebase, please?  This has not applied for some time, but
> I've made the situation worse with 4b203d499c61.  No need to bump
> again the module for this release cycle, we can stay at 1.7 for the
> new objects.
> --
> Michael

Thanks for the heads up! It is rebased, I also added
'CHECK_FOR_INTERRUPTS()' while looping over the 'NBuffers' regarding
the comment in the email [1].

[1] https://postgr.es/m/D5BB1D85-0F2A-419F-A7B1-426505525D3A%40gmail.com

-- 
Regards,
Nazir Bilal Yavuz
Microsoft