This is an automated email from the ASF dual-hosted git repository.
reshke pushed a commit to branch REL_2_STABLE
in repository https://gitbox.apache.org/repos/asf/cloudberry.git
The following commit(s) were added to refs/heads/REL_2_STABLE by this push:
new 0fd99be1177 Fix for CDBD expand with concurrent distributed tx (#1801)
0fd99be1177 is described below
commit 0fd99be1177f0630fdc26096be9d7a357920de6a
Author: reshke <[email protected]>
AuthorDate: Thu Jun 4 10:14:51 2026 +0500
Fix for CDBD expand with concurrent distributed tx (#1801)
An duct tape for this was already added as fc8aab8, through redo
path was not patched there. Copy same guard into
redoDistributedCommitRecord function boby.
---
src/backend/cdb/cdbdtxrecovery.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/src/backend/cdb/cdbdtxrecovery.c b/src/backend/cdb/cdbdtxrecovery.c
index 605ce323ddb..1082e5c0fe2 100644
--- a/src/backend/cdb/cdbdtxrecovery.c
+++ b/src/backend/cdb/cdbdtxrecovery.c
@@ -493,6 +493,17 @@ redoDistributedCommitRecord(DistributedTransactionId gxid)
int i;
bool is_hot_standby_qd = IS_HOT_STANDBY_QD();
+ /*
+ * The coordinator may execute write DTX during gpexpand, so the newly
+ * added segment may contain DTX info in checkpoint XLOG. However, this
step
+ * is useless and should be avoided for segments, or fatal may be
thrown since
+ * max_tm_gxacts is 0 in segments. See also fc8aab88d
+ */
+ if (ConvertMasterDataDirToSegment && !IS_QUERY_DISPATCHER())
+ {
+ return;
+ }
+
/*
* Only the startup process can be modifying shmNumCommittedGxacts
* and shmCommittedGxidArray. So should be OK reading the value w/o
lock.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
