From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
Subject: | pg_checksums? |
Date: | 2023-10-27 18:34:00 |
Message-ID: | 22272207-E6E5-4DD5-9BD4-5F6B647E2C3B@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I have a few questions about pg_checksums.
Long story short, checksums were disabled in our environment but are getting enabled now (again!) because of block corruptions which destroyed a few databases in a database cluster. And before you say "told you so", the decision to disable checksums was not mine. Some people just have to learn the hard way.
Anyway, re-enabling data checksums creates a few questions:
a) why isn't it possible to enable checksumming while a database cluster is up?
b) why isn't it possible to check whether checksums are enabled or not?
c) in a Patroni cluster consisting of a primary and a sync standby, is it safe to enable checksumming in the replica, then switch over and enable it in the ex-primary, i.e. now new replica, without any penalty? Or do I have to perform a reinit to really get them in sync again, though paronictl happily reports them to be in sync?
d) how long does it take to enable checksums in general? Minimizing down-time is crucial. Does it depend on the database cluster size, or the number of files it uses, or what can be taken as a criterion to estimate then necessary down-time.
Thanks in advance for your insights.
Cheers
Paul
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2023-10-27 19:02:57 | Re: pg_checksums? |
Previous Message | Peter J. Holzer | 2023-10-27 17:07:11 | Re: Disk wait problem... may not be hardware... |