Re: datachecksums: handle invalid and dropped databases during enable

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Nathan Bossart <nathandbossart(at)gmail(dot)com>
Cc: Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com>, 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 21:48:36
Message-ID: 6C5BFC06-94D9-438D-9E4E-FE1CAAA17C23@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 25 Aug 2026, at 21:32, Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
>
> Does this one deserve a mention on the open items wiki [0]?

I don't think this is an open item; the code as it stands reverts back to a
safe state in the case of a failed DROP. The same goes for if a user
terminates the worker process, maybe there is a UX change to consider in a
future version but it's not broken the way it is (as in, it reverts to a safe
state). Do you agree with this Zsolt or an I missing an active bug?

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2026-08-26 21:57:31 Re: [PATCH] pgcrypto: Ensure debug handler is reset on error in PGP functions
Previous Message Corey Huinker 2026-08-26 21:21:36 Re: pg_restore_attribute_stats() accepts non-finite values