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

Álvaro Herrera <alvherre@kurilemu.de>

From: Álvaro Herrera <alvherre@kurilemu.de>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: 'Vishal Prasanna' <vishal.g@zohocorp.com>, pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Date: 2026-06-10T13:04:48Z
Lists: pgsql-bugs
Hello,

On 2026-Mar-27, Hayato Kuroda (Fujitsu) wrote:

> Dear Vishal,
> 
> I noticed commitfest app got angry your patch, but your patch could still be applied.
> Per my understanding, cfbot tried to apply all patches to master but failed.
> Here are fixed version, only suffix is changed for some patches.

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.

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"I am amazed at [the pgsql-sql] mailing list for the wonderful support, and
lack of hesitasion in answering a lost soul's question, I just wished the rest
of the mailing list could be like this."                               (Fotis)
              https://postgr.es/m/200606261359.k5QDxE2p004593@auth-smtp.hol.gr



Commits

  1. logical decoding: Correctly free speculative insertion

  2. Fix memory counter update in ReorderBuffer.