Re: Problem Dropping a Database with users connected to it

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Eric Dorland <eric(dot)dorland(at)mcgill(dot)ca>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Problem Dropping a Database with users connected to it
Date: 2005-01-14 16:58:24
Message-ID: 20050114165824.GA26228@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Jan 14, 2005 at 11:16:16 -0500,
Eric Dorland <eric(dot)dorland(at)mcgill(dot)ca> 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Wes 2005-01-14 17:04:43 Re: [HACKERS] Much Ado About COUNT(*)
Previous Message Tom Lane 2005-01-14 16:57:08 Re: C locale + unicode