Horton

Re: dropdb --force

Thomas Munro <thomas.munro@gmail.com>

View thread View on postgr.es
From: Thomas Munro <thomas.munro@gmail.com>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Anthony Nowocien <anowocien@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Filip Rembiałkowski <filip.rembialkowski@gmail.com>
Date: 2019-08-01T07:02:12Z
Lists: pgsql-hackers 
On Thu, Jul 25, 2019 at 8:45 PM Pavel Stehule <pavel.stehule@gmail.com> wrote:
> čt 25. 7. 2019 v 5:11 odesílatel Tom Lane <tgl@sss.pgh.pa.us> napsal:
>> Pavel Stehule <pavel.stehule@gmail.com> writes:
>> > [ drop-database-force-20190708.patch ]
>>
>> I took a brief look at this, but I don't think it's really close to
>> being committable.

Hi Pavel,

The concept seems popular (I've wanted this myself), but it sounds
like it needs some more work.  I've moved this to the next CF.  If you
don't think you'll be able to work on it for the next CF, of course,
please feel free to change it to "Returned with feedback".

-- 
Thomas Munro
https://enterprisedb.com

Commits

  1. Add tests for '-f' option in dropdb utility.

  2. Move pump_until to TestLib.pm.

  3. Add the support for '-f' option in dropdb utility.

  4. Introduce the 'force' option for the Drop Database command.

  5. Improve CREATE/DROP/RENAME DATABASE so that when failing because the source