Re: datachecksums: handle invalid and dropped databases during enable

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Zsolt Parragi <zsolt(dot)parragi(at)percona(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:07:51
Message-ID: ao9jtwEhGTe0XVsW@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 26, 2026 at 11:06:20PM +0100, Zsolt Parragi wrote:
> 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.

Thanks for chiming in. I've removed the open item.

--
nathan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2026-08-26 22:10:58 Re: pg_plan_advice: fix empty FOREIGN_JOIN sublist validation
Previous Message Zsolt Parragi 2026-08-26 22:06:20 Re: datachecksums: handle invalid and dropped databases during enable