pgsql: Correct prune WAL record opcode name in comment

From: Melanie Plageman <melanieplageman(at)gmail(dot)com>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Correct prune WAL record opcode name in comment
Date: 2025-09-24 16:30:50
Message-ID: E1v1SOI-002LAq-0K@gemulon.postgresql.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Correct prune WAL record opcode name in comment

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(at)gmail(dot)com>
Reviewed-by: Andres Freund <andres(at)anarazel(dot)de>
Discussion: https://postgr.es/m/yn4zp35kkdsjx6wf47zcfmxgexxt4h2og47pvnw2x5ifyrs3qc%407uw6jyyxuyf7

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/ae8ea7278c16a23aa7dfb56c531706c18628ba55

Modified Files
--------------
src/backend/access/heap/pruneheap.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Fujii Masao 2025-09-24 16:39:39 pgsql: vacuumdb: Do not run VACUUM (ONLY_DATABASE_STATS) when --analyze
Previous Message Tom Lane 2025-09-24 16:28:35 pgsql: Ensure guc_tables.o's dependency on guc_tables.inc.c is known.