Re: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change

From: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
To: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
Cc: 'Vishal Prasanna' <vishal(dot)g(at)zohocorp(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
Date: 2026-06-16 18:22:16
Message-ID: ajF7NRf9IwBQb5gk@alvherre.pgsql
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2026-Jun-10, Álvaro Herrera wrote:

> Thanks. As far as I can tell this is just a leak, right? There's
> nothing that misbehaves when assertions are disabled, even with
> MEMORY_CONTEX_CHECKING -- it's just a small, very improbably mem leak.
>
> I'm tempted not to touch REL_14_STABLE with it in that case.

I ended up pushing to 14 after all, after I noticed that the code in
that branch is pretty much identical to what's in 15 -- it was only the
test code that required a separate patch file.

--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Álvaro Herrera 2026-06-16 18:36:29 Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.
Previous Message 王跃林 2026-06-16 11:29:35 Fw:Re: Fw: gbt_var_consistent in contrib/btree_gist/btree_utils_var.c has internal-node type confusion on the <> strategy, bypassing exclusion constraints