Search Postgresql Archives

Re: Problem Dropping a Database with users connected to it

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2005-01-14 at 10:58 -0600, Bruno Wolff III wrote:
> On Fri, Jan 14, 2005 at 11:16:16 -0500,
>   Eric Dorland <eric.dorland@xxxxxxxxx> wrote:
> > 
> > * Disconnecting all other users before dropping the db, but that doesn't
> > seem possible (I could start and stop the db, but that doesn't stop any
> > clients from just reconnecting right away).
> 
> You could use an alter pg_hba.conf file while doing the drop.
> 
> > * Just drop all the tables, etc. instead of dropping the db. There
> > doesn't seem to be a good way to do this except doing an explicit DROP
> > TABLE foo on all 200 tables. Is there a good recipe for this, an easy
> > way to get a listing of all the tables in a db?
> 
> If all of the tables are in the public schema, dropping that schema should
> cascade to dropping all of the tables.

I had not considered dropping the schema, but that sounds like a good
solution. I'll give it a shot.

-- 
Eric Dorland
eric.dorland@xxxxxxxxx
WCG
514.398-5023 ext. 09562


---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux