database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-26 12:21:12 +03:00
Code Activity

pg_waldump: Fix --bkp-details to not issue spurious newlines for FPWs.

Browse Source 
The additional newline seems to have accidentally been introduced in
2c03216d83, 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 2c03216d83.
This commit is contained in:
Andres Freund
2019-10-29 22:46:40 -07:00
parent 95f2efd504
commit bc4f56c181
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
src/bin/pg_xlogdump/pg_xlogdump.c
View File

@ -509,7 +509,7 @@ XLogDumpDisplayRecord(XLogDumpConfig *config, XLogReaderState *record)
if (record->blocks[block_id].bimg_info & if (record->blocks[block_id].bimg_info &
BKPIMAGE_IS_COMPRESSED) BKPIMAGE_IS_COMPRESSED)
{ {
printf(" (FPW); hole: offset: %u, length: %u, compression saved: %u\n", printf(" (FPW); hole: offset: %u, length: %u, compression saved: %u",
record->blocks[block_id].hole_offset, record->blocks[block_id].hole_offset,
record->blocks[block_id].hole_length, record->blocks[block_id].hole_length,
BLCKSZ - BLCKSZ -
@ -518,7 +518,7 @@ XLogDumpDisplayRecord(XLogDumpConfig *config, XLogReaderState *record)
} }
else else
{ {
printf(" (FPW); hole: offset: %u, length: %u\n", printf(" (FPW); hole: offset: %u, length: %u",
record->blocks[block_id].hole_offset, record->blocks[block_id].hole_offset,
record->blocks[block_id].hole_length); record->blocks[block_id].hole_length);
} }