Re: Incorrect "ERROR: database "xxx" is being accessed by other users"

From: "Dmitry Koterov" <dmitry(at)koterov(dot)ru>
To: "Michael Fuhr" <mike(at)fuhr(dot)org>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-general(at)postgresql(dot)org
Subject: Re: Incorrect "ERROR: database "xxx" is being accessed by other users"
Date: 2007-03-13 11:13:45
Message-ID: d7df81620703130413u4105c7d7m4eee1e2b6b7add3@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks a lot! All works!

So - I propose to change error message from

ERROR: database "xxx" is being accessed by other users

to

ERROR: database "xxx" is being accessed by other users or there are
prepared transactions exist (please use "SELECT * FROM pg_prepared_xacts"
and "ROLLBACK PREPARED ..." to fix this)

in a new PG version. Is it possible?

On 3/13/07, Michael Fuhr <mike(at)fuhr(dot)org> wrote:
>
> On Tue, Mar 13, 2007 at 11:41:46AM +0300, Dmitry Koterov wrote:
> > Yes, I have one!
> > How to remove it now? I tried DEALLOCATE for gid returned by
> >
> > select * from pg_prepared_xacts;
> >
> > but it says "prepared statement does not exist"...
>
> DEALLOCATE is for prepared *statements*; you have a prepared
> *transaction*. Connect to the database you're trying to drop and
> use ROLLBACK PREPARED or COMMIT PREPARED, then disconnect from that
> database and try dropping it again.
>
> --
> Michael Fuhr
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Guillaume Bog 2007-03-13 11:36:38 Re: finding a column by name in psql
Previous Message Michael Fuhr 2007-03-13 09:52:59 Re: Incorrect "ERROR: database "xxx" is being accessed by other users"