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 202602251653.e66kyhiyntlm@alvherre.pgsql
Whole thread Raw
In response to RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change  (Vishal Prasanna <vishal.g@zohocorp.com>)
Responses RE: [BUG] Assert failure in ReorderBufferReturnTXN during logical decoding due to leaked specinsert change
List pgsql-bugs
On 2026-Feb-25, Vishal Prasanna wrote:

> > It looks OK for me. In this case an argument should be reduced from 
> > ReorderBufferResetTXN(), right? It is harmless because the function is a static one.
> 
> Yes, the `specinsert` is no longer needed in
> `ReorderBufferResetTXN()`. Updated the patch where `specinsert`
> cleanup is now handled in the `PG_CATCH()` block of
> `ReorderBufferProcessTXN()`, so it is always freed before the if/else
> branch.

Please don't do this.  Changing the argument list of an exported
function is an ABI break.  That's an OK change to do in branch master
(to keep the interface clean), but for released branches it is not
welcome, because it causes problems for users that have extensions that
call the function and were compiled with its older definition.

-- 
Álvaro Herrera        Breisgau, Deutschland  —  https://www.EnterpriseDB.com/



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Major Version Upgrade failure due to orphan roles entries in catalog
Next
From: PG Bug reporting form
Date:
Subject: BUG #19416: Backend SIGSEGV in ExecShutdownHashJoin/ExecHashTableDetach/dsa_free