Re: Changing the state of data checksums in a running cluster
Andres Freund <andres@anarazel.de>
Hi, On 2026-04-05 00:27:00 +0200, Daniel Gustafsson wrote: > > On 4 Apr 2026, at 02:35, Daniel Gustafsson <daniel@yesql.se> wrote: > > > >> On 4 Apr 2026, at 00:59, Daniel Gustafsson <daniel@yesql.se> wrote: > >> > >>> On 3 Apr 2026, at 23:46, Daniel Gustafsson <daniel@yesql.se> wrote: > >>> > >>> After many more runs on CI I ended up pushing this version, and I see BF > >>> members being angry due the test not waiting for the launcher to exit. I am > >>> working on a fix right now. > >> > >> 0036232ba8f seems to have made the failing animals slightly happier, I will > >> continue to monitor the buildfarm for other fallout. > > > > The intermittent failure on kestrel implies timing similar to the one fixed in > > 0036232ba8fb28, a tentative fix is to make it part of waiting for an endstate > > (on or off) to make sure the cluster is always in the right state for new > > operations. Right now kestrel is the one which has been flapping, I'm waiting > > a bit to see if more will follow and give further clues. > > mylodon had the same failure, and I believe the bug is in my injection point > test code. I have a tentative fix in the attached refactoring which moves over > to using the injection_point extension module. It's still fairly rare so I'm > holding off for a little bit before pushing it to see if I can collect a little > bit more evidence. There are a lot checksum related errors on CI: https://cirrus-ci.com/task/4848298592305152 https://cirrus-ci.com/task/5338691381493760 https://cirrus-ci.com/task/6271077241847808 https://cirrus-ci.com/task/6150048418889728 They probably are mostly the issues you know about. It'd be nice to get them fixed soon-ish... Greetings, Andres Freund
Commits
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Use correct datatype for PID
- 0ca1b3010597 19 (unreleased) landed
-
Improve comments in online checksums code
- cd857dec0e0a 19 (unreleased) landed
-
Fix checksum state transition during promotion
- 5fee7cab1b87 19 (unreleased) landed
-
Fix regex searching for page verification failures in tests
- 486b9a9b9eb4 19 (unreleased) landed
-
Apply data-checksum worker throttling parameters
- 9a39056c418c 19 (unreleased) landed
-
Skip WAL for unlogged main fork during online checksum enable
- 2018bd616790 19 (unreleased) landed
-
Fix data_checksum GUC show_hook
- 75152c5dc5d3 19 (unreleased) landed
-
Improve database detection logic in datachecksumsworker
- 1df361e3d82c 19 (unreleased) landed
-
Improve handling of concurrent checksum requests
- bf25e5571b32 19 (unreleased) landed
-
Typo and spelling fixups for online checksums
- 381d19da1536 19 (unreleased) landed
-
Fix invalid checksum state transition in checkpoints
- 25b922ec5825 19 (unreleased) landed
-
Handle data_checksum state changes during launcher_exit
- 8fb8ded88956 19 (unreleased) landed
-
Test improvements for online checksums
- a0d8f4c1ae16 19 (unreleased) landed
-
Prevent pg_enable/disable_data_checksums() on standby
- b120358c612d 19 (unreleased) landed
-
Test stabilization for online checksums
- 07009121c235 19 (unreleased) landed
-
Make data checksum tests more resilient for slow machines
- 0036232ba8fb 19 (unreleased) landed
-
Formalize WAL record for XLOG_CHECKPOINT_REDO
- 097ab69d17f7 19 (unreleased) landed
-
Revert "Get rid of WALBufMappingLock"
- c13070a27b63 19 (unreleased) cited
-
Get rid of WALBufMappingLock
- bc22dc0e0ddc 18.0 cited
-
Improve grammar of options for command arrays in TAP tests
- ce1b0f9da03e 18.0 cited