pgsql: Correct prune WAL record opcode name in comment - Mailing list pgsql-committers

From Melanie Plageman
Subject pgsql: Correct prune WAL record opcode name in comment
Date
Msg-id E1v1SOI-002LAq-0K@gemulon.postgresql.org
Whole thread Raw
List 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@gmail.com>
Reviewed-by: Andres Freund <andres@anarazel.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(-)


pgsql-committers by date:

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