Re: BUG #19551: TRAP: failed Assert("max_pinned_buffers > 0")

From: Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: r(dot)zharkov(at)postgrespro(dot)ru, pgsql-bugs(at)lists(dot)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Subject: Re: BUG #19551: TRAP: failed Assert("max_pinned_buffers > 0")
Date: 2026-07-13 13:13:15
Message-ID: CAN55FZ3w6q_nT6tXxV4rgNh7KJCKMfkgwc+cg69cap-fFP0k9Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On Mon, 13 Jul 2026 at 16:01, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Nazir Bilal Yavuz <byavuz81(at)gmail(dot)com> writes:
> > On Sat, 11 Jul 2026 at 15:08, PG Bug reporting form
> > <noreply(at)postgresql(dot)org> wrote:
> >> This error occurred when attempting run the temp.sql regression test from
> >> the master branch on the REL_17_STABLE (#bab0a2db).
> >> It seems, REL_16_STABLE and REL_18_STABLE work fine.
>
> > Thank you for the reproducer script.
>
> > I think this is expected. If you disable asserts, you will see an
> > actual error message: 'ERROR: no empty local buffer available'. This
> > error message can be seen on both REL_16_STABLE and REL_18_STABLE too.
>
> The point is you're not supposed to be able to trigger an Assert from
> SQL.

I see. Thanks for the clarification.

--
Regards,
Nazir Bilal Yavuz
Microsoft

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Tom Lane 2026-07-13 13:01:26 Re: BUG #19551: TRAP: failed Assert("max_pinned_buffers > 0")