Re: Changing the state of data checksums in a running cluster

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Tomas Vondra <tomas(at)vondra(dot)me>, Bernd Helmle <mailings(at)oopsware(dot)de>, Michael Paquier <michael(at)paquier(dot)xyz>, Michael Banck <mbanck(at)gmx(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Changing the state of data checksums in a running cluster
Date: 2026-09-01 05:00:00
Message-ID: b4481314-b2da-4d88-baa4-b5d44c924caf@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hello Daniel,

30.08.2026 23:15, Daniel Gustafsson wrote:
>> Yes, this change makes the test pass (50 iterations) reliably for me.
> Cool, thanks for testing. Just so I understand, both the issues you had
> observed were fixed by this or just one of them?

Yes, both cases are not reproduced with the wait.

UPD: Sorry, I forgot to push Send yesterday.

Best regards,
Alexander

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Imran Zaheer 2026-09-01 05:06:40 Re: Failing assertion while taking a restartpoint during crash recovery
Previous Message Laurenz Albe 2026-09-01 04:58:57 Re: Adding a stored generated column without long-lived locks