Horton

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

Bernd Helmle <mailings@oopsware.de>

View thread
From: Bernd Helmle <mailings@oopsware.de>
To: Tomas Vondra <tomas@vondra.me>, Daniel Gustafsson <daniel@yesql.se>
Cc: Michael Paquier <michael@paquier.xyz>, Michael Banck <mbanck@gmx.net>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-07-11T15:53:58Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Use correct datatype for PID

  2. Improve comments in online checksums code

  3. Fix checksum state transition during promotion

  4. Fix regex searching for page verification failures in tests

  5. Apply data-checksum worker throttling parameters

  6. Skip WAL for unlogged main fork during online checksum enable

  7. Revert "Get rid of WALBufMappingLock"

  8. Get rid of WALBufMappingLock

  9. Improve grammar of options for command arrays in TAP tests

Attachments

Am Samstag, dem 15.03.2025 um 16:50 +0100 schrieb Tomas Vondra:
> 

> I wonder if this "time travel backwards" might be an issue for this
> too,
> because it might mean we end up picking the wrong
> data_checksum_version
> from the control file. In any case, if this happens, we don't get to
> the
> ControlFile->data_checksum_version update a bit further down. And
> there's another condition that can skip that.
> 
> 
> I'll continue investigating this next week, but at this point I'm
> quite
> confused and would be grateful for any insights ...
> 

Hi,

Since i wanted to dig a little deeper in this patch i took the
opportunity and rebased it to current master, hopefully not having
broken something seriously.

Thanks,
	Bernd