Re: Add information to rm_redo_error_callback() - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Add information to rm_redo_error_callback()
Date
Msg-id 20201001074109.GL8130@paquier.xyz
Whole thread Raw
In response to Re: Add information to rm_redo_error_callback()  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Add information to rm_redo_error_callback()  ("Drouvot, Bertrand" <bdrouvot@amazon.com>)
List pgsql-hackers
On Thu, Sep 24, 2020 at 03:03:46PM +0900, Michael Paquier wrote:
> Hmm.  I still think that knowing at least about a FPW could be an
> interesting piece of information even here.  Anyway, instead of
> copying a logic that exists already in xlog_outrec(), why not moving
> the block information print into a separate routine out of the
> WAL_DEBUG section, and just reuse the same format for the context of
> the redo error callback?  That would also be more consistent with what
> we do in pg_waldump where we don't show the fork name of a block when
> it is on a MAIN_FORKNUM.  And this would avoid a third copy of the
> same logic.  If we add the XID, previous LSN and the record length
> on the stack of what is printed, we could just reuse the existing
> routine, still that's perhaps too much information displayed.

Seeing nothing, I took a swing at that, and finished with the
attached that refactors the logic and prints the block information as
wanted.  Any objections to that?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: enable_incremental_sort changes query behavior
Next
From: Kyotaro Horiguchi
Date:
Subject: Re: Protect syscache from bloating with negative cache entries