summaryrefslogtreecommitdiff
path: root/src/backend/storage/ipc/standby.c
diff options
context:
space:
mode:
Diffstat (limited to 'src/backend/storage/ipc/standby.c')
-rw-r--r--src/backend/storage/ipc/standby.c6
1 files changed, 4 insertions, 2 deletions
diff --git a/src/backend/storage/ipc/standby.c b/src/backend/storage/ipc/standby.c
index 3f5df9a2e96..206fa2d69e6 100644
--- a/src/backend/storage/ipc/standby.c
+++ b/src/backend/storage/ipc/standby.c
@@ -270,8 +270,10 @@ ResolveRecoveryConflictWithSnapshot(TransactionId latestRemovedXid, RelFileNode
* If we get passed InvalidTransactionId then we are a little surprised,
* but it is theoretically possible in normal running. It also happens
* when replaying already applied WAL records after a standby crash or
- * restart. If latestRemovedXid is invalid then there is no conflict. That
- * rule applies across all record types that suffer from this conflict.
+ * restart, or when replaying an XLOG_HEAP2_VISIBLE record that marks as
+ * frozen a page which was already all-visible. If latestRemovedXid is
+ * invalid then there is no conflict. That rule applies across all record
+ * types that suffer from this conflict.
*/
if (!TransactionIdIsValid(latestRemovedXid))
return;