Re: Feature Request: DROP ALL FROM DATABASE database_name - Mailing list pgsql-hackers

From Marc G. Fournier
Subject Re: Feature Request: DROP ALL FROM DATABASE database_name
Date
Msg-id 20020109010848.D21205-100000@earth.hub.org
Whole thread Raw
In response to Re: Feature Request: DROP ALL FROM DATABASE database_name  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, 8 Jan 2002, Tom Lane wrote:

> Thomas Swan <tswan-lst@ics.olemiss.edu> writes:
> > This could be useful for cleaning out a database (sequences, triggers,
> > rules) without deleting it and without having to create it, thus
> > preserving permissions/owner information.
>
> What permissions/owner information?  There won't be any left if we
> remove everything in the database.
>
> Also, given the possibility that the database has been created from
> a nonempty template, it's less than clear exactly what should be
> removed.
>
> I'd say DROP and CREATE DATABASE is a perfectly presentable way of
> handling this.

From an ISP standpoint, this is something that I'd definitely love to see
... would save getting requests from users that don't have access to
anything but their database from having to ask me to DROP/CREATE their
database :)




pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: 7.1 vs. 7.2 on AIX 5L
Next
From: "Christopher Kings-Lynne"
Date:
Subject: postmaster vs. postgres