Re: WAL record CRC calculated incorrectly because of underlying buffer modification

From: vignesh C <vignesh21(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Greg Burd <greg(at)burd(dot)me>, pgsql-hackers(at)postgresql(dot)org, pgsql(at)j-davis(dot)com, thomas(dot)munro(at)gmail(dot)com, exclusion(at)gmail(dot)com, andres(at)anarazel(dot)de, amit(dot)kapila16(at)gmail(dot)com, hlinnaka(at)iki(dot)fi
Subject: Re: WAL record CRC calculated incorrectly because of underlying buffer modification
Date: 2026-11-02 13:25:49
Message-ID: CALDaNm1q0XRVMRNyB_zdNw13W7yQ_pdQ+jqQUyqnY=SCANZfuA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2 Nov 2026 at 16:31, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Mon, Nov 02, 2026 at 02:21:58PM +0530, vignesh C wrote:
> > I was wondering whether we should mention this in the release notes,
> > advising users to update standbys before primaries or disable
> > wal_consistency_checking on the primary until all nodes are updated.
>
> wal_consistency_checking is a developer option. I doubt that this is
> worth mentioning in the release notes: nobody should use it in
> production environments.

Thanks, that makes sense. Then nothing else is required for this.

Regards,
Vignesh

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2026-11-02 13:33:25 Re: Let's drop support for named POSIX semaphores
Previous Message Andrei Lepikhov 2026-11-02 13:10:52 Re: issues with eager aggregation