Re: GetBufferDescriptor() being called for local buffers from MarkBufferDirtyHint()

From: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: GetBufferDescriptor() being called for local buffers from MarkBufferDirtyHint()
Date: 2026-07-02 04:59:47
Message-ID: CAExHW5tprKEf1m7-bZ-38ntYt-mzroZd14eq-s7qTepkziUkuw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 2, 2026 at 10:16 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Wed, Jul 01, 2026 at 08:00:38PM +0530, Ayush Tiwari wrote:
> > v2 attached sets NLocBuffer = nbufs before the initialization loop, so the
> > loop can keep using GetLocalBufferDescriptor(), and drops the now-redundant
> > assignment at the end.
>
> Catching up with the latest activity of this thread now that v20 has
> opened up. That's kind of nice.
>
> I have been also reminded about BufferIsValid(), where we already have
> similar assertions. As a whole, that seems acceptable to me, and
> using unsigned still does not make much sense here.
>
> Any thoughts or objections regarding a HEAD-only change?

We usually do not backport changes to function definitions or new
assertions, unless they are critical to the fix. That is not the case
here. The functions have been in this state for a couple of releases
and we haven't heard any complaints. Overall HEAD-only is fine with
me.

If required we can always backport, the functions are static so they
won't cause an ABI break. The Assertions are applicable in those
branches as well.

--
Best Wishes,
Ashutosh Bapat

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Lakhin 2026-07-02 05:00:01 Re: Improving tracking/processing of buildfarm test failures
Previous Message Nisha Moond 2026-07-02 04:51:18 Re: Support EXCEPT for TABLES IN SCHEMA publications