| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Tomas Vondra <tomas(at)vondra(dot)me> |
| Cc: | 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: | 2025-08-27 11:00:04 |
| Message-ID: | 7357A519-3391-4F07-BC69-5C9C2B120792@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 27 Aug 2025, at 11:39, Tomas Vondra <tomas(at)vondra(dot)me> wrote:
> Just to be clear - I don't see any pg_checksums failures either. I only
> see failures in the standby log, and I don't think the script checks
> that (it probably should).
Right, that's what I'm been checking too. I have been considering adding
another background process for monitoring all the log entries but I just
thought of a much simpler solution. When the clusters are turned off we can
take the opportunity to slurp the log written since last restart and inspect
it. The attached adds this.
It would probably be good to at some point clean this up a little by placing
all of variables for a single node in an associative hash which can be passed
around, and place repeated code in subroutines etc..
--
Daniel Gustafsson
| Attachment | Content-Type | Size |
|---|---|---|
| v202508272-0001-Online-enabling-and-disabling-of-data-che.patch | application/octet-stream | 181.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dean Rasheed | 2025-08-27 11:12:56 | Re: Fix replica identity checks for MERGE command on published table. |
| Previous Message | Mihail Nikalayeu | 2025-08-27 10:55:12 | Re: Adding REPACK [concurrently] |