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 <[EMAIL PROTECTED]> 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 a
Eric Dorland <[EMAIL PROTECTED]> writes:
> 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 m
On Fri, Jan 14, 2005 at 11:16:16 -0500,
Eric Dorland <[EMAIL PROTECTED]> 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 a
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.
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
