Re: pg_waldump erroneously outputs newline for FPWs, and anotherminor bug - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: pg_waldump erroneously outputs newline for FPWs, and anotherminor bug
Date
Msg-id CAH2-Wzn7Aw60HFvc=VrXpzqJAphPtuN2qLMj03FyyykMcBPMeA@mail.gmail.com
Whole thread Raw
In response to pg_waldump erroneously outputs newline for FPWs, and another minorbug  (Andres Freund <andres@anarazel.de>)
Responses Re: pg_waldump erroneously outputs newline for FPWs, and anotherminor bug
List pgsql-hackers
On Tue, Oct 29, 2019 at 4:33 PM Andres Freund <andres@anarazel.de> wrote:
> Does anybody have an opinion about fixing it just in master or also
> backpatching it? I guess there could be people having written parsers
> for the waldump output?  I'm inclined to backpatch.

The same commit from Heikki omitted one field from that record, for no
good reason. I backpatched a bugfix to the output format for nbtree
page splits a few weeks ago, fixing that problem. I agree that we
should also backpatch this bugfix.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Connections hang indefinitely while taking a gin index's LWLockbuffer_content lock(PG10.7)
Next
From: Andres Freund
Date:
Subject: Make StringInfo available to frontend code.