Re: Enabling checksums on a streaming replica

From: Grigory Smolkin <g(dot)smolkin(at)postgrespro(dot)ru>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Enabling checksums on a streaming replica
Date: 2019-06-26 16:37:10
Message-ID: 92db1a5e-109e-c7b1-504b-7a897ba7d732@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello!

Very interesting idea, but what about full page writes, that comes from
master?
Can they be a problem?

On 6/26/19 6:32 PM, Brad Nicholson wrote:
>
> I'm wondering about the validity of using the pg_checksums utility to
> enable checksum's on a streaming replication standby, and then
> promoting that standby as a way to enable checksums on existing clusters.
>
> I've tested the process out, and it "works" (by works I mean doesn't
> blow up or log any errors). But this seems far enough outside of
> supported territory that I'm curious what others think.
>
> The process is:
>
> - Primary with checksums off
> - create a streaming replica off that primary
> - stop the secondary
> - enable checksums on the secondary with the pg_checksums utility
> - start the replica
> - promote the replica
>
> I've thrown load at it while the it was replicating from checksums off
> -> checksums on, promoted it, and verified the checksums after with
> pg_checksums.
>
> Any thoughts on this approach?
>
> Thanks,
> Brad
>
--
Grigory Smolkin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Brad Nicholson 2019-06-26 18:08:19 Re: Re: Enabling checksums on a streaming replica
Previous Message Peter Geoghegan 2019-06-26 16:09:08 Re: REINDEX : new parameter to preserve current average leaf density as new implicit FILLFACTOR