Re: datachecksums: handle invalid and dropped databases during enable

From: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Daniel Gustafsson <daniel(at)yesql(dot)se>, Alexander Lakhin <exclusion(at)gmail(dot)com>, Tomas Vondra <tomas(at)vondra(dot)me>, "Jonathan Gonzalez V(dot)" <jonathan(dot)abdiel(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: datachecksums: handle invalid and dropped databases during enable
Date: 2026-08-26 22:06:20
Message-ID: CAN4CZFON4JAEmhX0mJi5y03PfbfpRtJZbDudS8ZeYYNdNWkktA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I agree. It is about automatically continuing instead of stopping in a
very unlikely scenario (DROP DATABASE FORCE failing), and also a more
questionable ux change on how manual process termination behaves. Both
the current and patched versions behave correctly.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-08-26 22:07:51 Re: datachecksums: handle invalid and dropped databases during enable
Previous Message Daniel Gustafsson 2026-08-26 22:05:28 Re: Changing the state of data checksums in a running cluster