Re: Add information to rm_redo_error_callback()

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: Add information to rm_redo_error_callback()
Дата
Msg-id 20200811062956.GI17986@paquier.xyz
обсуждение исходный текст
Ответ на Re: Add information to rm_redo_error_callback()  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
Ответы Re: Add information to rm_redo_error_callback()  (Masahiko Sawada <masahiko.sawada@2ndquadrant.com>)
Список 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

Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: torikoshia
Дата:
Сообщение: Re: Creating a function for exposing memory usage of backend process
Следующее
От: Masahiko Sawada
Дата:
Сообщение: Re: massive FPI_FOR_HINT load after promote