Re: DROP DATABASE is interruptible
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Andres Freund <andres@anarazel.de>
Cc: Thomas Munro <thomas.munro@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
Evgeny Morozov <postgresql3@realityexists.net>,
Tom Lane <tgl@sss.pgh.pa.us>
Date: 2023-07-14T08:35:42Z
Lists: pgsql-hackers
> On 13 Jul 2023, at 22:52, Andres Freund <andres@anarazel.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
Commits
-
pg_dump: tests: Correct test condition for invalid databases
- 881defde944c 16.1 landed
- 6a3b19bbefd7 11.22 landed
- fd7a114dbb4e 12.17 landed
- d1c76fdec375 13.13 landed
- 4dfb610822d5 14.10 landed
- 9dc3c5472ed9 15.5 landed
- 849d367ff9a2 17.0 landed
-
Handle DROP DATABASE getting interrupted
- f66403749df7 15.4 landed
- 1c38e7ae17b6 11.21 landed
- 034a9fcd2bb8 12.16 landed
- 81ce000067e3 13.12 landed
- d11efe830385 14.9 landed
- a4b4cc1d60f7 16.0 landed
- c66a7d75e652 17.0 landed