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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: vignesh C <vignesh21(at)gmail(dot)com>
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 11:01:46
Message-ID: auhtmn6IcB9O6Tto@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jelte Fennema-Nio 2026-11-02 11:05:05 Re: Commitfest app changes deployed on November 2nd
Previous Message Álvaro Herrera 2026-11-02 11:01:11 Re: A gap in preventing bogus parameterizations in a798660ebe3