From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: pg_checksums?
Date: Sun, 29 Oct 2023 10:37:19 -0500
Message-ID: <11f5795f-ae2c-4123-93e7-b42d4a1115d7@gmail.com> (raw)
In-Reply-To: <81D43A87-7D3D-4F81-B462-641F15B5E332@gmail.com>
References: <22272207-E6E5-4DD5-9BD4-5F6B647E2C3B@gmail.com>
<0D18D31E-EF52-434D-875C-08BEC8DDD553@yesql.se>
<ZTwpx1sCIu-4EgRH@momjian.us>
<AB7D1C87-F9E6-4068-9AA9-8591C82CF9CC@gmail.com>
<20231029014310.7pbdfhincj2tds4l@hjp.at>
<81D43A87-7D3D-4F81-B462-641F15B5E332@gmail.com>
On 10/29/23 04:11, Paul Förster wrote:
> Hi Peter
>
>> On Oct 29, 2023, at 02:43, Peter J. Holzer <hjp-pgsql@hjp.at> wrote:
>> I don't think so. AFAIK Replication keeps the data files in sync on a
>> bit-for-bit level and turning on checksums changes the data layout.
>> Running a cluster where one node has checksums and the other doesn't
>> would result in a complete mess.
> I agree with the last sentence. This is why I asked if it is safe to enable checksums on a replica, switch over and then do it again on the ex primary, i.e. now new replica without doing a reinit.
For that to work, the secondary files would have to remain identical to the
primary files. Theoretically that _should_ happen, but it might not, or
whatever command that enables checksums after the fact might have a sanity
check.
As for safety, what do you mean by "safe"?
--
Born in Arizona, moved to Babylonia.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ronljohnsonjr@gmail.com
Subject: Re: pg_checksums?
In-Reply-To: <11f5795f-ae2c-4123-93e7-b42d4a1115d7@gmail.com>
References: <22272207-E6E5-4DD5-9BD4-5F6B647E2C3B@gmail.com> <0D18D31E-EF52-434D-875C-08BEC8DDD553@yesql.se> <ZTwpx1sCIu-4EgRH@momjian.us> <AB7D1C87-F9E6-4068-9AA9-8591C82CF9CC@gmail.com> <20231029014310.7pbdfhincj2tds4l@hjp.at> <81D43A87-7D3D-4F81-B462-641F15B5E332@gmail.com> <11f5795f-ae2c-4123-93e7-b42d4a1115d7@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox