Re: Problem Dropping a Database with users connected to it - Mailing list pgsql-general

From Fernando Schapachnik
Subject Re: Problem Dropping a Database with users connected to it
Date
Msg-id 20050114163747.GI362@bal740r0.mecon.gov.ar
Whole thread Raw
In response to Problem Dropping a Database with users connected to it  (Eric Dorland <eric.dorland@mcgill.ca>)
List pgsql-general
Just kill the processes. You can grep for postgres AND idle. It doesn't prevent
new connections, but doesn't look like an issue in your scenario. If you need
that, you can restart with a copy of pg_hba.conf that only allows localhost, do
your drop & recreate, and then restart again.


Regards.

En un mensaje anterior, Eric Dorland escribió:
> Hi,
>
> I'm basically trying to do what the subject says, through various means
> with no success. The basic situation is that every night we recreate our
> development database with a complete copy of our live data. The problem
> is some of the developers (well me especially) leave open connections to
> the DB at night, so the database drop fails. Now that's ok, but I need
> some sort of alternative... I thought of:
>
> * 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).

pgsql-general by date:

Previous
From: John Sidney-Woollett
Date:
Subject: C locale + unicode
Next
From: "J. Greenlees"
Date:
Subject: ntfs for windows port rc5-2