Re:BUG #18241: PushTransaction may cause Standby to execute ItemIdMarkDead

From: feichanghong <feichanghong(at)qq(dot)com>
To: feichanghong <feichanghong(at)qq(dot)com>, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re:BUG #18241: PushTransaction may cause Standby to execute ItemIdMarkDead
Date: 2023-12-11 12:13:23
Message-ID: tencent_C4D907A5093C071A029712E73B43C6512706@qq.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

&gt; We have analyzed the cause of the problem: The value of
&gt;&nbsp;IndexScanDesc-&gt;xactStartedInRecovery is a key condition for determining
&gt;&nbsp;whether an index item can be marked as DEAD. And it depends on
&gt;&nbsp;CurrentTransactionState-&gt;startedInRecovery. However, PushTransaction does
&gt;&nbsp;not assign a value to startedInRecovery when modifying
&gt;&nbsp;CurrentTransactionState.
The attached patch has been verified to resolve the mentioned issue.

Attachment Content-Type Size
fix_PushTransaction.patch application/octet-stream 601 bytes

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dean Rasheed 2023-12-11 12:53:35 Re: BUG #18238: Cross-partitition MERGE/UPDATE with delete-preventing trigger leads to incorrect memory access
Previous Message PG Bug reporting form 2023-12-11 12:06:28 BUG #18241: PushTransaction may cause Standby to execute ItemIdMarkDead