Re: pg_waldump erroneously outputs newline for FPWs, and another minor bug

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: pg_waldump erroneously outputs newline for FPWs, and another minor bug
Date: 2019-10-29 23:42:07
Message-ID: CAH2-Wzn7Aw60HFvc=VrXpzqJAphPtuN2qLMj03FyyykMcBPMeA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 29, 2019 at 4:33 PM Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-10-30 00:10:01 Make StringInfo available to frontend code.
Previous Message Peter Geoghegan 2019-10-29 23:34:38 Re: Connections hang indefinitely while taking a gin index's LWLock buffer_content lock(PG10.7)