Correct prune WAL record opcode name in comment
authorMelanie Plageman <melanieplageman@gmail.com>
Wed, 24 Sep 2025 16:29:13 +0000 (12:29 -0400)
committerMelanie Plageman <melanieplageman@gmail.com>
Wed, 24 Sep 2025 16:29:56 +0000 (12:29 -0400)
f83d709760d8 incorrectly refers to a XLOG_HEAP2_PRUNE_FREEZE WAL record
opcode. No such code exists. The relevant opcodes are
XLOG_HEAP2_PRUNE_ON_ACCESS, XLOG_HEAP2_PRUNE_VACUUM_SCAN, and
XLOG_HEAP2_PRUNE_VACUUM_CLEANUP. Correct it.

Author: Melanie Plageman <melanieplageman@gmail.com>
Reviewed-by: Andres Freund <andres@anarazel.de>
Discussion: https://postgr.es/m/yn4zp35kkdsjx6wf47zcfmxgexxt4h2og47pvnw2x5ifyrs3qc%407uw6jyyxuyf7

src/backend/access/heap/pruneheap.c

index 7ebd22f00a37045b0eafa70c49f4eb79dece5846..d8ea0c78f77cf7b344518ca38c95e135b522ed9e 100644 (file)
@@ -794,7 +794,7 @@ heap_page_prune_and_freeze(Relation relation, Buffer buffer,
        MarkBufferDirty(buffer);
 
        /*
-        * Emit a WAL XLOG_HEAP2_PRUNE_FREEZE record showing what we did
+        * Emit a WAL XLOG_HEAP2_PRUNE* record showing what we did
         */
        if (RelationNeedsWAL(relation))
        {
@@ -2026,7 +2026,7 @@ heap_log_freeze_plan(HeapTupleFreeze *tuples, int ntuples,
 }
 
 /*
- * Write an XLOG_HEAP2_PRUNE_FREEZE WAL record
+ * Write an XLOG_HEAP2_PRUNE* WAL record
  *
  * This is used for several different page maintenance operations:
  *