Re: BUG #19006: Assert(BufferIsPinned) in BufferGetBlockNumber() is triggered for forwarded buffer - Mailing list pgsql-bugs

From Xuneng Zhou
Subject Re: BUG #19006: Assert(BufferIsPinned) in BufferGetBlockNumber() is triggered for forwarded buffer
Date
Msg-id CABPTF7V7HeZmpYK-zdjq4bS4UBGjRH-2niF4bdi_jgQr7Ujy+Q@mail.gmail.com
Whole thread Raw
In response to Re: BUG #19006: Assert(BufferIsPinned) in BufferGetBlockNumber() is triggered for forwarded buffer  (Michael Paquier <michael@paquier.xyz>)
List pgsql-bugs
Hi,

On Wed, Aug 6, 2025 at 4:40 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Tue, Aug 05, 2025 at 12:43:06AM -0400, Tom Lane wrote:
> > I've not looked at the issue actually being fixed, but a drive-by
> > comment: these loops
> >
> > +     for (int i = 0; i < stream->forwarded_buffers; ++i)
> > +             Assert(BufferGetBlockNumber(stream->buffers[stream->next_buffer_index + i]) ==
> > +                        stream->pending_read_blocknum + i);
> >
> > should be wrapped in "#ifdef USE_ASSERT_CHECKING".  Maybe the
> > compiler is smart enough to throw away the useless looping logic
> > in a production build, or maybe it isn't.
>
> I'd bet it is usually not that smart..  Embedding these in an extra
> #ifdef is a sound defense IMO.
> --
> Michael

+1

Best,
Xuneng



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute
Next
From: hubert depesz lubaczewski
Date:
Subject: Re: BUG #19014: Automatic aggressive VACUUM on template0 and template1 pg_shdepend runs every minute