From: | Bernd Helmle <mailings(at)oopsware(dot)de> |
---|---|
To: | Tomas Vondra <tomas(at)vondra(dot)me>, Daniel Gustafsson <daniel(at)yesql(dot)se> |
Cc: | 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: | 2025-07-11 15:53:58 |
Message-ID: | 2864a79c1ab628f609104a955a725879fdf5486f.camel@oopsware.de |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
Attachment | Content-Type | Size |
---|---|---|
v20250711-0001-Online-enabling-and-disabling-of-data-checksums.patch | text/x-patch | 149.7 KB |
v20250711-0002-Reviewfixups.patch | text/x-patch | 4.6 KB |
v20250711-0003-Rework-handling-of-procsignalbarrier-and-local-cache.patch | text/x-patch | 8.7 KB |
v20250711-0004-debug-stuff.patch | text/x-patch | 17.3 KB |
test.sh | application/x-shellscript | 8.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2025-07-11 15:57:29 | Re: [Question] Window Function Results without ORDER BY Clause |
Previous Message | Nitin Motiani | 2025-07-11 15:47:00 | Re: Horribly slow pg_upgrade performance with many Large Objects |