Horton

Re: Offline enabling/disabling of data checksums

Fabien COELHO <coelho@cri.ensmp.fr>

View thread View on postgr.es
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Michael Paquier <michael@paquier.xyz>
Cc: Andres Freund <andres@anarazel.de>, Michael Banck <michael.banck@credativ.de>, Magnus Hagander <magnus@hagander.net>, Sergei Kornilov <sk@zsrv.org>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>
Date: 2019-03-21T09:57:41Z
Lists: pgsql-hackers 
> Anyway, as this stuff is very useful for upgrade scenarios 
> a-la-pg_upgrade, for backup validation and as it does not produce false 
> positives, I would really like to get something committed for v12 in its 
> simplest form...

Fine with me, the detailed doc is not a showstopper and can be improved 
later one.

> Are there any recommendations that people would like to add to the 
> documentation?

For me, I just want at least a clear warning on potential risks.

-- 
Fabien.

Commits

  1. Reorganize Notes section in documentation of pg_checksums

  2. Add option -N/--no-sync to pg_checksums

  3. Add options to enable and disable checksums in pg_checksums

  4. Refactor more code logic to update the control file

  5. Rename pg_verify_checksums to pg_checksums

  6. Fix cross-version compatibility checks of pg_verify_checksums

  7. Add routine able to update the control file to src/common/