aboutsummaryrefslogtreecommitdiff
path: root/src
diff options
context:
space:
mode:
authorSimon Riggs <simon@2ndQuadrant.com>2017-03-22 16:58:12 +0000
committerSimon Riggs <simon@2ndQuadrant.com>2017-03-22 16:58:12 +0000
commitc137c68ea6bfe860c3e5f4edee7031e136ba4f0c (patch)
treeee5aac69295a30fef11eea847428585650c4bc99 /src
parentaf4b1a0869bd3bb52e5f662e4491554b7f611489 (diff)
downloadpostgresql-c137c68ea6bfe860c3e5f4edee7031e136ba4f0c.tar.gz
postgresql-c137c68ea6bfe860c3e5f4edee7031e136ba4f0c.zip
Correct erroneous comment in GetOldestXmin()
Craig Ringer
Diffstat (limited to 'src')
-rw-r--r--src/backend/storage/ipc/procarray.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/backend/storage/ipc/procarray.c b/src/backend/storage/ipc/procarray.c
index 3e562d3a545..40c3247d4b8 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