| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Sergei Kornilov <sk(at)zsrv(dot)org>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Michael Banck <michael(dot)banck(at)credativ(dot)de>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Offline enabling/disabling of data checksums |
| Date: | 2019-03-14 14:28:15 |
| Message-ID: | 20190314142815.GD32045@msg.df7cb.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Re: Magnus Hagander 2019-03-14 <CABUevEx7QZLOjWDvwTdm1VM+mjsDm7=ZmB8qck7nDmcHEY5O5g(at)mail(dot)gmail(dot)com>
> Are you suggesting we should support running with a master with checksums
> on and a standby with checksums off in the same cluster? That seems.. Very
> fragile.
The case "shut down master and standby, run pg_checksums on both, and
start them again" should be supported. That seems safe to do, and a
real-world use case.
Changing the system id to a random number would complicate this.
(Horrible idea: maybe just adding 1 (= checksum version) to the system
id would work?)
Christoph
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2019-03-14 14:32:22 | Re: Offline enabling/disabling of data checksums |
| Previous Message | Magnus Hagander | 2019-03-14 14:26:53 | Re: Offline enabling/disabling of data checksums |