Re: Progress reporting for pg_verify_checksums
Michael Paquier <michael@paquier.xyz>
From: Michael Paquier <michael@paquier.xyz>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Michael Banck <michael.banck@credativ.de>, Kyotaro HORIGUCHI <horiguchi.kyotaro@lab.ntt.co.jp>, alvherre@2ndquadrant.com, mailings@oopsware.de, thomas.munro@enterprisedb.com, pgsql-hackers@postgresql.org
Date: 2019-04-03T01:49:19Z
Lists: pgsql-hackers
On Tue, Apr 02, 2019 at 10:10:34AM +0200, Fabien COELHO wrote: > For online, we should want throttling so that the check can have a reduced > performance impact when scrubbing. Yes. Throttling is a necessary property in my opinion, perhaps in combination with some autovacuum-like options to only trigger the checks for a relation after a certain amout of activity has happened on it. -- Michael
Commits
-
Add progress reporting to pg_checksums
- 280e5f14056b 12.0 landed
-
Fix thinko when bumping on temporary directories in pg_verify_checksums
- da453004869d 11.3 landed
-
Fix thinko when bumping on temporary directories in pg_checksums
- 6eebfdc38b17 12.0 landed