Re: BUG #19551: TRAP: failed Assert("max_pinned_buffers > 0") - Mailing list pgsql-bugs

From Nazir Bilal Yavuz
Subject Re: BUG #19551: TRAP: failed Assert("max_pinned_buffers > 0")
Date
Msg-id CAN55FZ2P0KbZ4vUOegAj-nuFndF5cHj=WSR8q=mg8dth5AQN5w@mail.gmail.com
Whole thread
List pgsql-bugs
Hi,

On Sat, 11 Jul 2026 at 15:08, PG Bug reporting form
<noreply@postgresql.org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference:      19551
> Logged by:          Roman Zharkov
> Email address:      r.zharkov@postgrespro.ru
> PostgreSQL version: 17.10
> Operating system:   WSL2 on Windows 11
> Description:
>
> Hello,
> 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.


--
Regards,
Nazir Bilal Yavuz
Microsoft



pgsql-bugs by date:

Previous
From: Karen Huang
Date:
Subject: Re: BUG #19541: Postgresql failed to run 150+ tests on both debug and release configurations with VS 2026 on Windows
Next
From: Nazir Bilal Yavuz
Date:
Subject: Re: BUG #19551: TRAP: failed Assert("max_pinned_buffers > 0")