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 20200811062956.GI17986@paquier.xyz
Whole thread Raw
In response to Re: Add information to rm_redo_error_callback()  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
Responses Re: Add information to rm_redo_error_callback()  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
List pgsql-hackers
On Tue, Aug 11, 2020 at 02:45:50PM +0900, Masahiko Sawada wrote:
> Thank you for updating the patch!
>
> The patch looks good to me. I've set this patch as Ready for Committer.

+       for (block_id = 0; block_id <= record->max_block_id; block_id++)
+       {
+               RelFileNode rnode;
+               ForkNumber forknum;
+               BlockNumber blknum;

Doesn't this potentially create duplicate information in some of the
RM's desc() callbacks, and are we sure that the information provided
is worth having for all the RMs?  As one example, gin_desc() looks at
some of the block information, so there are overlaps.  It may be
worth thinking about showing more information for has_image and
apply_image if a block is in_use?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: torikoshia
Date:
Subject: Re: Creating a function for exposing memory usage of backend process
Next
From: Masahiko Sawada
Date:
Subject: Re: massive FPI_FOR_HINT load after promote