From d2ca63fb8cf49202b3f43da8d9350d73948d5db3 Mon Sep 17 00:00:00 2001
From: Teja Mupparti <temuppar@microsoft.com>
Date: Tue, 24 Dec 2024 14:42:15 -0800
Subject: [PATCH] For scenarios, such as, Bug 3697586: Server crashes when
 assigning distributed transaction: Raise an ERROR instead of a crash

(cherry picked from commit ab7c13beb5ec7415dc881c9b72ac0881b9daf4e5)
---
 src/backend/distributed/transaction/backend_data.c | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/src/backend/distributed/transaction/backend_data.c b/src/backend/distributed/transaction/backend_data.c
index 384954b81..866b18fd2 100644
--- a/src/backend/distributed/transaction/backend_data.c
+++ b/src/backend/distributed/transaction/backend_data.c
@@ -855,6 +855,16 @@ GetCurrentDistributedTransactionId(void)
 void
 AssignDistributedTransactionId(void)
 {
+	/*
+	 * MyBackendData should always be available. However, we observed some
+	 * crashes where certain hooks were not executed.
+	 * Bug 3697586: Server crashes when assigning distributed transaction
+	 */
+	if (!MyBackendData)
+	{
+		ereport(ERROR, (errmsg("backend is not ready for distributed transactions")));
+	}
+
 	pg_atomic_uint64 *transactionNumberSequence =
 		&backendManagementShmemData->nextTransactionNumber;