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.1904020805030.10740@lancre
Whole thread Raw
In response to Re: Progress reporting for pg_verify_checksums  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Progress reporting for pg_verify_checksums
List pgsql-hackers
Bonjour Michaël,

>> Maybe it should be -P X where X is the expected
>> delay in seconds. Pgbench progress reporting on initialization basically
>> outputs 10 rows per second, probably it is too much.
>
> I cannot say for pgbench.  I personally think that's a lot but you are
> the one who wrote it as such I guess.

Nope, this was way before I intervened. ISTM that a patch was submitted to 
get per second or slower progress reporting on the initalization, and it 
was rejected. Now that there are many SSD, maybe I could bring it back. An 
issue with pbbench is that the reported time and progress is for the 
insertion phase only, but PK and other FK declaration take as much time 
and are not included, so I'm not sure it can be much better.

For pg_checksums, probably some improvement patch will be submitted later, 
if someone feels like it.

-- 
Fabien.

pgsql-hackers by date:

Previous
From: Haribabu Kommi
Date:
Subject: Re: Pluggable Storage - Andres's take
Next
From: Darafei "Komяpa" Praliaskouski
Date:
Subject: Re: Compressed TOAST Slicing