Re: Feature Request: DROP ALL FROM DATABASE database_name

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Swan <tswan-lst(at)ics(dot)olemiss(dot)edu>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Feature Request: DROP ALL FROM DATABASE database_name
Date: 2002-01-08 23:50:15
Message-ID: 1226.1010533815@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Swan 2002-01-08 23:57:34 Re: Feature Request: DROP ALL FROM DATABASE database_name
Previous Message Bruce Momjian 2002-01-08 23:33:56 Re: Feature Request: DROP ALL FROM DATABASE database_name