[PATCH] standby: Clarify recovery conflict comment

From: Ankush Mondal <ankushmondal1y2t(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Ankush Mondal <ankushmondal1y2t(at)gmail(dot)com>
Subject: [PATCH] standby: Clarify recovery conflict comment
Date: 2026-11-13 08:19:31
Message-ID: 20261113081931.171931-1-ankushmondal1y2t@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

---
src/backend/storage/ipc/standby.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/backend/storage/ipc/standby.c b/src/backend/storage/ipc/standby.c
index 7f011e04990..b603f02167b 100644
--- a/src/backend/storage/ipc/standby.c
+++ b/src/backend/storage/ipc/standby.c
@@ -803,7 +803,8 @@ ResolveRecoveryConflictWithBufferPin(void)
if (GetCurrentTimestamp() >= ltime && ltime != 0)
{
/*
- * We're already behind, so clear a path as quickly as possible.
+ * The standby delay has expired, so signal conflicting backends
+ * to release their buffer pins as quickly as possible.
*/
SendRecoveryConflictWithBufferPin(RECOVERY_CONFLICT_BUFFERPIN);
}
--
2.43.0

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jingtang Zhang 2026-11-13 08:44:29 transaction_timeout is not enforced during ClientWrite
Previous Message Xuneng Zhou 2026-11-13 07:43:20 Re: Deadlock detector fails to activate on a hot standby replica