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

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Andres Freund <andres(at)anarazel(dot)de>
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, 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-10-29 02:19:14
Message-ID: auKtIrePSfV5THtK@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 28, 2026 at 11:57:53AM -0400, Andres Freund wrote:
> Fair enough. I guess I'd hoped that one of the folks involved in adding the
> hash index WAL logging would chime in and fix this properly.

If input does not show up, I see nothing to do here except somebody
else popping up to take responsibility for the change. Actually, I
may not mind, this stuff is annoying..

Applied the workaround down to v17 for now.

> Ceterum censeo index access/hash esse delendum.

I doubt we would be able to do that, if ever.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2026-10-29 02:27:24 Re: WAL record CRC calculated incorrectly because of underlying buffer modification
Previous Message shihao zhong 2026-10-29 02:11:20 Re: [PG19] pg_upgrade --check passes, then the upgrade fails