Re: Add force option to dropdb - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Add force option to dropdb
Date
Msg-id CA+TgmoZVkbkSmk-PKEsAvCNcb5GJrM0iPODx0Mn0D8cXFMqe-g@mail.gmail.com
Whole thread Raw
In response to Re: Add force option to dropdb  (salah jubeh <s_jubeh@yahoo.com>)
Responses Re: Add force option to dropdb  (salah jubeh <s_jubeh@yahoo.com>)
List pgsql-hackers
On Tue, Jan 28, 2014 at 9:01 AM, salah jubeh <s_jubeh@yahoo.com> wrote:
> Hello Sawada,
>
>>- This patch is not patched to master branch
> Sorry, My mistake
>>//new connections are not allowed
> Corrected.
>
> I hope now the patch in better state, if somthing left, I will be glad to
> fix it
> Regards

I'm not particularly in favor of implementing this as client-side
functionality, because then it's only available to people who use that
particular client.  Simon Riggs proposed a server-side option to the
DROP DATABASE command some time ago, and I think that might be the way
to go.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: updated emacs configuration
Next
From: Amit Kapila
Date:
Subject: Re: [bug fix] pg_ctl always uses the same event source