Re: Feature Request: DROP ALL FROM DATABASE database_name

From: "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thomas Swan <tswan-lst(at)ics(dot)olemiss(dot)edu>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Feature Request: DROP ALL FROM DATABASE database_name
Date: 2002-01-09 05:11:11
Message-ID: 20020109010848.D21205-100000@earth.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 8 Jan 2002, Tom Lane wrote:

> Thomas Swan <tswan-lst(at)ics(dot)olemiss(dot)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 :)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2002-01-09 05:38:21 postmaster vs. postgres
Previous Message computertechnology 2002-01-09 04:00:00 Commercial: New Book!! PostgreSQL book is released into the market