public inbox for [email protected]  

help / color / mirror / Atom feed

From: Andreas Karlsson <[email protected]>
To: Tomas Vondra <[email protected]>
To: Daniel Gustafsson <[email protected]>
Cc: Bernd Helmle <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: Michael Banck <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Changing the state of data checksums in a running cluster
Date: Fri, 21 Nov 2025 01:44:31 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On 11/20/25 11:34 AM, Tomas Vondra wrote:
> On 11/19/25 22:03, Andreas Karlsson wrote:
>> Hi,
>>
>> I have been following these discussions but not read the patch in detail.
>>
>> This patch makes me worried especially with the new issues recently
>> uncovered. This was already a quite big patch and to fix these issues it
>> will likely have to become even bigger and given how this would become a
>> very rarely stressed code paths I wonder if we can actually ever become
>> confident that the patch works in all edge cases.
>>
>> Something like this need to be easy to understand for us to have any
>> hope at all to be comfortable in the correctness. Can we actually do that?
>>
> 
> How's this different from any other complex patch? We get more familiar
> with the problem during review, identify issues, improve the patch to
> address them. And then again and again.

The difference I see is in how rarely anyone actually switches checksum 
state in a production database, especially now that we enabled them by 
default. A complex and rarely stressed code path is a minefield.

Andreas

view thread (58+ messages)  latest in thread

reply

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 using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Changing the state of data checksums in a running cluster
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox