From: Simon Riggs <simon@2ndQuadrant.com>
Date: Wed, 22 Mar 2017 16:58:12 +0000 (+0000)
Subject: Correct erroneous comment in GetOldestXmin()
X-Git-Tag: REL_10_BETA1~557
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=c137c68ea6bfe860c3e5f4edee7031e136ba4f0c;p=postgresql

Correct erroneous comment in GetOldestXmin()

Craig Ringer
---

diff --git a/src/backend/storage/ipc/procarray.c b/src/backend/storage/ipc/procarray.c
index 3e562d3a54..40c3247d4b 100644
--- a/src/backend/storage/ipc/procarray.c
+++ b/src/backend/storage/ipc/procarray.c
@@ -1294,6 +1294,7 @@ TransactionIdIsActive(TransactionId xid)
  * in the master but are still being replayed on the standby, thus possibly
  * making the GetOldestXmin reading go backwards.  In this case there is a
  * possibility that we lose data that the standby would like to have, but
+ * unless the standby uses a replication slot to make its xmin persistent
  * there is little we can do about that --- data is only protected if the
  * walsender runs continuously while queries are executed on the standby.
  * (The Hot Standby code deals with such cases by failing standby queries