Re: Add information to rm_redo_error_callback()
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Masahiko Sawada <masahiko.sawada@2ndquadrant.com>
Cc: "Drouvot, Bertrand" <bdrouvot@amazon.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-08-11T06:29:56Z
Lists: 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
Commits
-
Add block information in error context of WAL REDO apply loop
- 9d0bd95fa90a 14.0 landed