`DROP DATABASE RESTRICT` ?

From: Brennan Vincent <brennan(at)materialize(dot)io>
To: pgsql-general(at)postgresql(dot)org
Cc: Nikhil Benesch <benesch(at)materialize(dot)io>
Subject: `DROP DATABASE RESTRICT` ?
Date: 2020-03-02 21:03:58
Message-ID: CA+OW2AAPbxriULHcYJP2VL-CQZb=zonZRRg=m2zn84wn-OA5-g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello all,

I was wondering if there is some reason why Postgres doesn't support a
`RESTRICT` option that would refuse to drop a database if it contains
any schemas or objects, similarly to the semantics of `DROP SCHEMA
[...] RESTRICT`.

Is there a fundamental reason not to support it, or is it just that
nobody has implemented it yet?

Thanks
Brennan

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2020-03-02 21:11:19 Re: Detecting which columns a query will modify in a function called by a trigger
Previous Message Tim Cross 2020-03-02 20:50:33 Re: Detecting which columns a query will modify in a function called by a trigger