Re: BUG #19839: Assert in ReorderBufferRestoreCleanup for aborted, spilled transaction

From: Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>
To: Zhijie Hou <houzhijie22(at)gmail(dot)com>
Cc: Atisss hh <125atishprak(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19839: Assert in ReorderBufferRestoreCleanup for aborted, spilled transaction
Date: 2026-11-09 14:47:17
Message-ID: avHc9Z9u7Ns6xD43@bdtpg
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi,

On Mon, Nov 09, 2026 at 07:46:59PM +0800, Zhijie Hou wrote:
> Thanks for the review. It looks like Atisss's update patches didn't reach
> the list, probably a missing Reply-All, so I'm helping to attach the same
> patches (provided by Atisss) here.

LGTM, just one nit about:

+ /*
+ * Mark the transaction as serialized only if something was written,
+ * and only after the check above. final_lsn is advanced for each
+ * change written, so a transaction that wrote nothing, such as a
+ * subtransaction without decoded changes, would be marked with an
+ * invalid final_lsn, and ReorderBufferRestoreCleanup() would later
+ * fail on it.
+ */

It looks lengthy and “the check above” is ambiguous. I'm not sure we need a new
comment here, maybe just replace the existing?

/* update the statistics iff we have spilled anything */

with

/* update the statistics and mark the transaction serialized iff we spilled */

Regards,

--
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message Jesper St John 2026-11-09 13:19:29 Re: Timing issue in pg_basebackup