Skip to content

Commit 8220011

Browse files
committed
pg_waldump: Fix --bkp-details to not issue spurious newlines for FPWs.
The additional newline seems to have accidentally been introduced in 2c03216, in 9.5. The newline is only issued when an FPW is present for the block reference. While there could be an argument that removing the newlines in the back branches could cause a problem for somebody parsing the pg_waldump output, the likelihood of that seems small enough. It seems at least equally likely that the randomness of when newlines are issued causes problems. Author: Andres Freund Discussion: https://postgr.es/m/20191029233341.4gnyau7e5v2lh5sc@alap3.anarazel.de Backpatch: 9.5, like 2c03216.
1 parent e3ff8c3 commit 8220011

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/bin/pg_waldump/pg_waldump.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -515,7 +515,7 @@ XLogDumpDisplayRecord(XLogDumpConfig *config, XLogReaderState *record)
515515
BKPIMAGE_IS_COMPRESSED)
516516
{
517517
printf(" (FPW%s); hole: offset: %u, length: %u, "
518-
"compression saved: %u\n",
518+
"compression saved: %u",
519519
XLogRecBlockImageApply(record, block_id) ?
520520
"" : " for WAL verification",
521521
record->blocks[block_id].hole_offset,
@@ -526,7 +526,7 @@ XLogDumpDisplayRecord(XLogDumpConfig *config, XLogReaderState *record)
526526
}
527527
else
528528
{
529-
printf(" (FPW%s); hole: offset: %u, length: %u\n",
529+
printf(" (FPW%s); hole: offset: %u, length: %u",
530530
XLogRecBlockImageApply(record, block_id) ?
531531
"" : " for WAL verification",
532532
record->blocks[block_id].hole_offset,

0 commit comments

Comments
 (0)