RE: Fix pg_checksums progress report - Mailing list pgsql-hackers

From
Subject RE: Fix pg_checksums progress report
Date
Msg-id TYAPR01MB2896A762DDA55506F98F3F57C47A9@TYAPR01MB2896.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: Fix pg_checksums progress report  (Fujii Masao <masao.fujii@oss.nttdata.com>)
Responses Re: Fix pg_checksums progress report  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
>-----Original Message-----
>From: Fujii Masao <masao.fujii@oss.nttdata.com>
>Sent: Friday, April 2, 2021 2:39 PM
>To: Shinya11.Kato@nttdata.com; pgsql-hackers@postgresql.org
>Subject: Re: Fix pg_checksums progress report
>
>
>
>On 2021/04/02 14:23, Shinya11.Kato@nttdata.com wrote:
>> Hi,
>>
>> I found a problem with the pg_checksums.c.
>>
>> The total_size is calculated by scanning the directory.
>> The current_size is calculated by scanning the files, but the current_size does
>not include the size of NewPages.
>>
>> This may cause pg_checksums progress report to not be 100%.
>> I have attached a patch that fixes this.
>
>Thanks for the report and patch!
>
>I could reproduce this issue and confirmed that the patch fixes it.
>
>Regarding the patch, I think that it's better to add the comment about why
>current_size needs to be counted including new pages.

Thanks for your review.
I added a comment to the patch, and attached the new patch.

Regards,
Shinya Kato


Attachment

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: Fix typo in verify_heapam.c
Next
From: Amit Langote
Date:
Subject: Re: making update/delete of inheritance trees scale better