Re: DROP DATABASE is interruptible

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Evgeny Morozov <postgresql3(at)realityexists(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: DROP DATABASE is interruptible
Date: 2023-07-14 08:35:42
Message-ID: 742B4436-A3AF-47AD-AF1B-31FE36DE0BD0@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 13 Jul 2023, at 22:52, Andres Freund <andres(at)anarazel(dot)de> wrote:
> On 2023-07-12 11:54:18 +0200, Daniel Gustafsson wrote:

>> Looking more at this I wonder if we in HEAD should make this a bit nicer by
>> extending the --check phase to catch this? I did a quick hack along these
>> lines in the 0003 commit attached here (0001 and 0002 are your unchanged
>> patches, just added for consistency and to be CFBot compatible). If done it
>> could be a separate commit to make the 0002 patch backport cleaner of course.
>
> I don't really have an opinion on that, tbh...

Fair enough. Thinking more on it I think it has merits, so I will submit that
patch in its own thread on -hackers.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Hayato Kuroda (Fujitsu) 2023-07-14 08:45:43 RE: doc: clarify the limitation for logical replication when REPILICA IDENTITY is FULL
Previous Message Daniel Gustafsson 2023-07-14 08:29:53 Re: 16beta2 SQL parser: different defaults on absent_on_null