Re: Offline enabling/disabling of data checksums

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Sergei Kornilov <sk@zsrv.org>

Cc: Michael Banck <michael.banck@credativ.de>, Magnus Hagander <magnus@hagander.net>, Fabien COELHO <coelho@cri.ensmp.fr>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>

Date: 2019-03-13T12:23:01Z

Lists: pgsql-hackers

On Wed, Mar 13, 2019 at 02:43:39PM +0300, Sergei Kornilov wrote:
> Seems good. And I think we need backpath this check to pg11. similar
> to cross-version compatibility checks 

Good point raised, a backpatch looks adapted.  It would be nice to get
into something more dynamic, but pg_checksum_block() uses directly
BLCKSZ :(
--
Michael

Commits

Reorganize Notes section in documentation of pg_checksums
- a7cc52370b2b 12.0 landed
Add option -N/--no-sync to pg_checksums
- e0090c869008 12.0 landed
Add options to enable and disable checksums in pg_checksums
- ed308d783790 12.0 landed
Refactor more code logic to update the control file
- 8b938d36f744 12.0 landed
Rename pg_verify_checksums to pg_checksums
- 6dd263cfaa84 12.0 landed
Fix cross-version compatibility checks of pg_verify_checksums
- 501f58359b59 11.3 landed
- c9ae7f704c67 12.0 landed
Add routine able to update the control file to src/common/
- ce6afc6823fb 12.0 landed