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 15:15:37 |
Message-ID: | 4614561A-6176-4136-BA96-74B05A7B6B5C@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Peter,
> On Oct 29, 2023, at 11:49, Peter J. Holzer <hjp-pgsql(at)hjp(dot)at> wrote:
>
> It *might* work if there are zero writes on the primary during the
> downtime of the replica (because those writes couldn't be replicated),
> but that seems hard to ensure. Even if you could get away with making
> the primary read-only (is this even possible?) I wouldn't have much
> confidence in the result and reinit the (new) replica anyway.
As soon as I stop the replica to enable checksums, even writes can't get replicated anymore. So during enabling checksums, a replica is definitely protected against modifications by its primary, simply because it's down. The modifications of the primary are applied to the replica when it comes back online. So, I don't see a problem at this particular stage.
My fear is merely that enabling checksums does something to the physical state of the data files which are not compatible with the other side. Like for example manipulate the file headers in some way.
Maybe this question is better suited for the admin list than this general list?
Cheers
Paul
From | Date | Subject | |
---|---|---|---|
Next Message | Peter J. Holzer | 2023-10-29 15:16:05 | Re: [SOLVED?] Re: Disk wait problem... not hardware... |
Previous Message | Peter J. Holzer | 2023-10-29 15:00:46 | Re: Disk wait problem... may not be hardware... |