Gregory Stark wrote:
It seems there's something wrong with CheckOtherDBBackends() but I haven't
exactly figured out what. There are no other sessions but drop database keeps
saying regression is being accessed by other users. I do see Autovacuum
touching tables in regression but
Maybe put the whole thing into the ERROR message instead of having a
separate DETAIL line?
ERROR: database %s is being accessed by %d session(s)
-or-
ERROR: database %s' is being accessed by %d prepared transaction(s)
-or-
ERROR: database %s' is being accessed by %d session(s) and %d
prepared
Russell Smith [EMAIL PROTECTED] writes:
Gregory Stark wrote:
It seems there's something wrong with CheckOtherDBBackends() but I haven't
exactly figured out what. There are no other sessions but drop database keeps
saying regression is being accessed by other users. I do see Autovacuum
It seems there's something wrong with CheckOtherDBBackends() but I haven't
exactly figured out what. There are no other sessions but drop database keeps
saying regression is being accessed by other users. I do see Autovacuum
touching tables in regression but CheckOtherDBBackends() is supposed to
Gregory Stark wrote:
It seems there's something wrong with CheckOtherDBBackends() but I haven't
exactly figured out what. There are no other sessions but drop database keeps
saying regression is being accessed by other users. I do see Autovacuum
touching tables in regression but
On Mon, Aug 04, 2008 at 11:51:35AM +0100, Gregory Stark wrote:
It seems there's something wrong with CheckOtherDBBackends() but I haven't
exactly figured out what. There are no other sessions but drop database keeps
saying regression is being accessed by other users.
Are any prepared
Michael Fuhr [EMAIL PROTECTED] writes:
On Mon, Aug 04, 2008 at 11:51:35AM +0100, Gregory Stark wrote:
It seems there's something wrong with CheckOtherDBBackends() but I haven't
exactly figured out what. There are no other sessions but drop database keeps
saying regression is being accessed by
Alvaro Herrera [EMAIL PROTECTED] writes:
The buildfarm would be all red if this wasn't something local to your
installation, I think. Maybe you should get gdb on the backend and set
a breakpoint on errfinish, or maybe step into CheckOtherDBBackends to
see why it isn't working.
Michael Fuhr
Gregory Stark wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
The buildfarm would be all red if this wasn't something local to your
installation, I think. Maybe you should get gdb on the backend and set
a breakpoint on errfinish, or maybe step into CheckOtherDBBackends to
see why it
Gregory Stark wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
The buildfarm would be all red if this wasn't something local to your
installation, I think. Maybe you should get gdb on the backend and set
a breakpoint on errfinish, or maybe step into CheckOtherDBBackends to
see why it
Andrew Dunstan [EMAIL PROTECTED] writes:
Gregory Stark wrote:
Michael Fuhr solved it so this is academic but, the buildfarm runs make
installcheck? I thought it just ran make check
It runs both.
It also runs contrib installcheck, which will most definitely exercise
DROP DATABASE.
Gregory Stark [EMAIL PROTECTED] writes:
Michael Fuhr [EMAIL PROTECTED] writes:
Are any prepared transactions still open?
Uh, yes, I did notice that but didn't put two and two together. That does make
sense now that you mention it.
I've been bit by that too, and so have other people. Maybe
Tom Lane wrote:
Gregory Stark [EMAIL PROTECTED] writes:
Michael Fuhr [EMAIL PROTECTED] writes:
Are any prepared transactions still open?
Uh, yes, I did notice that but didn't put two and two together. That does make
sense now that you mention it.
I've been bit by that too, and so have
Heikki Linnakangas [EMAIL PROTECTED] writes:
Tom Lane wrote:
I've been bit by that too, and so have other people. Maybe it'd be
worth the trouble to improve the message so that it explicitly tells you
when there are prepared transactions blocking the DROP.
Yes, that should be easy enough.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tom Lane wrote:
ERROR: database %s is being accessed by other users
DETAIL: There are %d session(s) and %d prepared transaction(s) using the
database.
I'm aware that this phrasing might not translate very nicely ... anyone
have a suggestion
Jens-Wolfhard Schicke [EMAIL PROTECTED] writes:
Tom Lane wrote:
ERROR: database %s is being accessed by other users
DETAIL: There are %d session(s) and %d prepared transaction(s) using the
database.
I'm aware that this phrasing might not translate very nicely ... anyone
have a suggestion
16 matches
Mail list logo
