Horton

Re: dropdb --force

Amit Kapila <amit.kapila16@gmail.com>

View thread View on postgr.es
From: Amit Kapila <amit.kapila16@gmail.com>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, vignesh C <vignesh21@gmail.com>, Dilip Kumar <dilipbalaut@gmail.com>, Ryan Lambert <ryan@rustprooflabs.com>, Thomas Munro <thomas.munro@gmail.com>, Anthony Nowocien <anowocien@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Filip Rembiałkowski <filip.rembialkowski@gmail.com>
Date: 2019-11-11T03:15:23Z
Lists: pgsql-hackers

Attachments

On Fri, Nov 8, 2019 at 4:57 PM Pavel Stehule <pavel.stehule@gmail.com> wrote:
>
> pá 8. 11. 2019 v 11:50 odesílatel Amit Kapila <amit.kapila16@gmail.com> napsal:
>>
>> Thanks, but are you planning to look at the other thread mentioned in
>> my previous email?  We need to finish that before this.
>
>
> I check it now - it has sense. the described switch can protect users against useless client killing.
>

I have committed that patch.  Please find the rebased patch attached.
Additionally, I ran the pgindent.  I will wait for two days and see if
you or anyone else has more inputs on the patch, if not, then I will
take one more pass and commit it on Wednesday morning.

-- 
With Regards,
Amit Kapila.
EnterpriseDB: http://www.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