| 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 22:02:46 |
| Message-ID: | 7044CCF7-7A3D-4258-A591-63D3C070D257@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 26 Aug 2026, at 23:59, Nathan Bossart <nathandbossart(at)gmail(dot)com> wrote:
>
> On Wed, Aug 26, 2026 at 11:48:36PM +0200, Daniel Gustafsson wrote:
>>> 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?
>
> Okay. I added one before you sent this message. Provided Zsolt agrees, I
> will remove it.
+1, sounds good.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2026-08-26 22:05:28 | Re: Changing the state of data checksums in a running cluster |
| Previous Message | surya poondla | 2026-08-26 22:02:00 | Re: BUG #19369: Not documented that io_uring on kernel versions between 5.1 and below 5.6 does not work |