| From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
|---|---|
| To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Michael Banck <michael(dot)banck(at)credativ(dot)de>, Magnus Hagander <magnus(at)hagander(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, Postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Offline enabling/disabling of data checksums |
| Date: | 2019-01-08 15:41:35 |
| Message-ID: | 457698805e88b7692300586bef905c1f9cac72e1.camel@oopsware.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Am Dienstag, den 08.01.2019, 16:17 +0100 schrieb Fabien COELHO:
> > > Adding a new state to ControlFileData which would prevent it from
> > > starting?
> >
> > 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.
Bernd.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2019-01-08 15:45:49 | Re: Offline enabling/disabling of data checksums |
| Previous Message | Tom Lane | 2019-01-08 15:29:06 | Re: Fast path for empty relids in check_outerjoin_delay() |