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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
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-08-30 20:15:27
Message-ID: 6D2C5247-8857-4A04-A3E9-D52142149845@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 29 Aug 2026, at 07:00, Alexander Lakhin <exclusion(at)gmail(dot)com> wrote:
> 28.08.2026 22:07, Daniel Gustafsson пишет:

>> -disable_data_checksums($node);
>> +disable_data_checksums($node, wait => 1);
>
> 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?

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Rithvika Devisetti 2026-08-30 20:35:08 Re: WAIT FOR command should do some query jumbling
Previous Message Daniel Gustafsson 2026-08-30 20:14:17 Re: Online enable/disable data checksums functions return success even when the launcher fails to start