From: | Paul Förster <paul(dot)foerster(at)gmail(dot)com> |
---|---|
To: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_checksums? |
Date: | 2023-10-29 18:01:43 |
Message-ID: | 39A3E175-E161-4325-A4AE-41B088FFADF6@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Ron,
> On Oct 29, 2023, at 16:38, Peter J. Holzer <hjp-pgsql(at)hjp(dot)at> wrote:
> And this is where it would break down. The modifications can't be
> applied to the replica any more because the replica now contains
> checksums and the modifications don't. In the best case the replica
> would catch the discrepancy and refuse to apply the modifications which
> would lead to the loss of these modifications. In the worst case it
> would apply them anyway causing severe data corruption.
...
> Not just the file headers. Every single data block.
>
> (Ok, it looks like the space for the checksum is reserved even if
> checksums aren't enabled[1]. So at least pg_checksums doesn't have to
> move data around to enable them. But overwriting a page with a checksum
> with one without one would still be bad.)
Those are the kind of answers and insights I was looking for. Thank you very much.
Ok, I will do a reinit then.
Cheers
Paul
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2023-10-29 18:26:27 | Re: pg_checksums? |
Previous Message | Paul Förster | 2023-10-29 17:57:15 | Re: pg_checksums? |