Re: Offline enabling/disabling of data checksums - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: Offline enabling/disabling of data checksums
Date
Msg-id alpine.DEB.2.21.1901081644220.32421@lancre
Whole thread Raw
In response to Re: Offline enabling/disabling of data checksums  (Bernd Helmle <mailings@oopsware.de>)
List pgsql-hackers
>>> But then you have to make sure the control flag gets cleared in any
>>> case pg_verify_checksums crashes somehow or gets SIGKILL'ed ...
>>
>> The usual approach is a restart with some --force option?
>>
>>> Setting the checksum flag is done after having finished all blocks, so 
>>> there is no problem.
>>
>> There is also a problem if the db is started while the checksum is 
>> being enabled.
>
> What i mean is that interrupting pg_verify_checksums won't leave 
> pg_control in a state where starting the cluster won't work without any 
> further interaction.

Yep, I understood that, and agree that a way out is needed, hence the 
--force option suggestion.

-- 
Fabien.


pgsql-hackers by date:

Previous
From: Bernd Helmle
Date:
Subject: Re: Offline enabling/disabling of data checksums
Next
From: Andrew Dunstan
Date:
Subject: Re: reducing the footprint of ScanKeyword (was Re: Large writablevariables)