pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed

From: Bernd Helmle <mailings@oopsware.de>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Michael Banck <michael.banck@credativ.de>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Postgres hackers <pgsql-hackers@postgresql.org>
Subject: Re: Offline enabling/disabling of data checksums
Date: Tue, 08 Jan 2019 16:41:35 +0100
Message-ID: <457698805e88b7692300586bef905c1f9cac72e1.camel@oopsware.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1901081614210.32421@lancre>
References: <20181221201616.GD4974@nighthawk.caipicrew.dd-dns.de>
	<alpine.DEB.2.21.1812261900400.32444@lancre>
	<20181227011534.GD2106@paquier.xyz>
	<CABUevEwbPVR_6Uv4D44fCd9tB_=aFxG4awUx+DJawD8_speuCA@mail.gmail.com>
	<alpine.DEB.2.21.1812271206340.32444@lancre>
	<1546945543.32387.8.camel@credativ.de>
	<alpine.DEB.2.21.1901081505010.32421@lancre>
	<65e4f3684f7563acc8b309393b8e14388b5eae0d.camel@oopsware.de>
	<alpine.DEB.2.21.1901081614210.32421@lancre>

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.

view thread (149+ messages)  latest in thread

Message-ID: <457698805e88b7692300586bef905c1f9cac72e1.camel@oopsware.de>
Permalink:  ../457698805e88b7692300586bef905c1f9cac72e1.camel@oopsware.de/
Also on:    postgresql.org/message-id/457698805e88b7692300586bef905c1f9cac72e1.camel@oopsware.de

copy link · copy postgr.es

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: mailings@oopsware.de, coelho@cri.ensmp.fr, michael.banck@credativ.de, magnus@hagander.net, michael@paquier.xyz
  Subject: Re: Offline enabling/disabling of data checksums
  In-Reply-To: <457698805e88b7692300586bef905c1f9cac72e1.camel@oopsware.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox