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 Banck <michael.banck@credativ.de>
Cc: Magnus Hagander <magnus@hagander.net>, Michael Paquier <michael@paquier.xyz>, Postgres hackers <pgsql-hackers@postgresql.org>
Date: 2019-01-08T14:09:03Z
Lists: pgsql-hackers 


> One difference between pg_rewind and pg_checksums is that the latter
> potentially runs for a longer time (or rather a non-trivial amount of
> time, compared to pg_rewind), so the margin of error of another DBA
> saying "oh, that DB is down, let me start it again" might be much
> higher.
>
> The question is how to reliably do this in an acceptable way? Just
> faking a postmaster.pid sounds pretty hackish to me, do you have any
> suggestions here?

Adding a new state to ControlFileData which would prevent it from 
starting?

-- 
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/