dropdb --force - Mailing list pgsql-hackers

From Filip Rembiałkowski
Subject dropdb --force
Date
Msg-id CAP_rwwmLJJbn70vLOZFpxGw3XD7nLB_7+NKz46H5EOO2k5H7OQ@mail.gmail.com
Whole thread Raw
Responses Re: dropdb --force  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: dropdb --force  (David Fetter <david@fetter.org>)
List pgsql-hackers
Hi,

I propose a simple patch (works-for-me), which adds --force (-f)
option to dropdb utility.

Pros:  This seems to be a desired option for many sysadmins, as this
thread proves: https://dba.stackexchange.com/questions/11893/force-drop-db-while-others-may-be-connected
Cons: another possible foot-gun for the unwary.

Obviously this patch needs some more work (see TODO note inside).

Please share opinions if this makes sense at all, and has any chance
going upstream.

The regression tests is simplistic, please help with an example of
multi-session test so I can follow.


Thanks,
Filip

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Some memory allocations in gin fastupdate code are a bit brain dead
Next
From: Alexey Kondratov
Date:
Subject: Re: PATCH: logical_work_mem and logical streaming of largein-progress transactions