Re: dropdb --force

Pavel Stehule <pavel.stehule@gmail.com>

From: Pavel Stehule <pavel.stehule@gmail.com>

To: vignesh C <vignesh21@gmail.com>

Cc: Ryan Lambert <ryan@rustprooflabs.com>, Tom Lane <tgl@sss.pgh.pa.us>, 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-09-18T18:43:41Z

Lists: pgsql-hackers

Attachments

drop-database-force-20190918-1.patch (text/x-patch) patch

Hi

I am sending updated version - the changes against last patch are two. I
use pg_terminate_backed for killing other terminates like Tom proposed. I
am not sure if it is 100% practical - on second hand the necessary right to
kill other sessions is  almost available - and consistency with
pg_terminal_backend has sense. More - native implementation is
significantly better then solution implemented outer. I fixed docs little
bit - the timeout for logout (as reaction on SIGTERM is only 5 sec).

Regards

Pavel

Commits

Add tests for '-f' option in dropdb utility.
- 8a7e9e9dad56 13.0 landed
Move pump_until to TestLib.pm.
- 290acac92b1d 13.0 landed
Add the support for '-f' option in dropdb utility.
- 80e05a088e4e 13.0 landed
Introduce the 'force' option for the Drop Database command.
- 1379fd537f9f 13.0 landed
Improve CREATE/DROP/RENAME DATABASE so that when failing because the source
- 4abd7b49f1e9 8.4.0 cited