Re: Progress reporting for pg_verify_checksums - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: Progress reporting for pg_verify_checksums
Date
Msg-id alpine.DEB.2.21.1903130719110.4059@lancre
Whole thread Raw
In response to Re: Progress reporting for pg_verify_checksums  (Michael Banck <michael.banck@credativ.de>)
Responses Re: Progress reporting for pg_verify_checksums
List pgsql-hackers
Hallo Michael,

>> I would bother rounding down < 100% to 100, because then you would get
>>
>>    1560/1492 MB (100\%, X MB/s)
>>
>> which is kind of silly.
>
> No, we cap the total_size to current_size so you won't see that (but
> total_size will potentially gradually increase). pg_basebackup has the
> same behaviour.

Ok.

> Because I implemented I/O throttling for pg_checksums

Great!

> New patch attached.

Does not apply because of the renaming committed by Michaël.

Could you rebase?

-- 
Fabien.

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PATCH] remove repetitive characters in fdwhandler.sgml
Next
From: David Rowley
Date:
Subject: Re: [HACKERS] PATCH: multivariate histograms and MCV lists