Andres Freund bc4f56c181 pg_waldump: Fix --bkp-details to not issue spurious newlines for FPWs. ... 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.		2019-10-29 22:54:36 -07:00
..
.gitignore	Generic Messages for Logical Decoding	2016-04-06 10:05:41 +01:00
compat.c	Use snprintf not sprintf in pg_waldump's timestamptz_to_str.	2018-06-16 14:45:47 -04:00
Makefile	Sort $(wildcard) output where needed for reproducible build output.	2016-01-05 15:47:05 -05:00
pg_xlogdump.c	pg_waldump: Fix --bkp-details to not issue spurious newlines for FPWs.	2019-10-29 22:54:36 -07:00
rmgrdesc.c	Generic Messages for Logical Decoding	2016-04-06 10:05:41 +01:00
rmgrdesc.h	Move pg_xlogdump from contrib/ to src/bin/	2015-04-21 19:03:49 -04:00