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 :)
Marc, I agree. One of the disadvantages of using PostgreSQL in a multiuser
multidatabase environment is the user and access controls that are currently
available in PostgreSQL.