Skip to content

Commit d4b5206

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 4ab353c commit d4b5206

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
@@ -600,7 +600,7 @@ XLogDumpDisplayRecord(XLogDumpConfig *config, XLogReaderState *record)
600600
BKPIMAGE_IS_COMPRESSED)
601601
{
602602
printf(" (FPW%s); hole: offset: %u, length: %u, "
603-
"compression saved: %u\n",
603+
"compression saved: %u",
604604
XLogRecBlockImageApply(record, block_id) ?
605605
"" : " for WAL verification",
606606
record->blocks[block_id].hole_offset,
@@ -611,7 +611,7 @@ XLogDumpDisplayRecord(XLogDumpConfig *config, XLogReaderState *record)
611611
}
612612
else
613613
{
614-
printf(" (FPW%s); hole: offset: %u, length: %u\n",
614+
printf(" (FPW%s); hole: offset: %u, length: %u",
615615
XLogRecBlockImageApply(record, block_id) ?
616616
"" : " for WAL verification",
617617
record->blocks[block_id].hole_offset,

0 commit comments

Comments
 (0)