Re: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change - Mailing list pgsql-bugs

From Álvaro Herrera
Subject Re: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
Date
Msg-id ajF7NRf9IwBQb5gk@alvherre.pgsql
Whole thread
In response to Re: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change  (Álvaro Herrera <alvherre@kurilemu.de>)
Responses RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
List 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/



pgsql-bugs by date:

Previous
From: 王跃林
Date:
Subject: 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
Next
From: Álvaro Herrera
Date:
Subject: Re: BUG #19521: After a minor PostgreSQL update from 14.22 to 14.23, the database goes into an infinite loop.