Re: Progress reporting for pg_verify_checksums - Mailing list pgsql-hackers

From Michael Banck
Subject Re: Progress reporting for pg_verify_checksums
Date
Msg-id 1554213779.4884.76.camel@credativ.de
Whole thread Raw
In response to Re: Progress reporting for pg_verify_checksums  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Progress reporting for pg_verify_checksums
List pgsql-hackers
Hi,

Am Dienstag, den 02.04.2019, 15:56 +0900 schrieb Michael Paquier:
> Regarding all this tooling around checksums.  With v12, enabling
> checksums with no actual downtime is doable with a primary-standby
> deployment using physical replication and one planned failover

Can you explain in more detail how this would work? I thought we came to
the conclusion (and the documentation seems to indicate so), that you
should stop all participating instances of a cluster and then enable
checksums on all of them, which would impose a downtime.


Michael

-- 
Michael Banck
Projektleiter / Senior Berater
Tel.: +49 2166 9901-171
Fax:  +49 2166 9901-100
Email: michael.banck@credativ.de

credativ GmbH, HRB Mönchengladbach 12080
USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer

Unser Umgang mit personenbezogenen Daten unterliegt
folgenden Bestimmungen: https://www.credativ.de/datenschutz



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: "could not reattach to shared memory" on buildfarm member dory
Next
From: Tom Lane
Date:
Subject: Re: "could not reattach to shared memory" on buildfarm member dory