> Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> >> If it is stuck, on which lock(s)?
>
> > How can I check it?
>
> The 'stuck' message should at least give you a code location...
Here is the actual message:
FATAL: s_lock(0x2ac2d016) at spin.c:158, stuck spinlock. Aborting.
Last several queries before stuck spinlock are:
DEBUG: query: update branches set bbalance = bbalance + 436 where bid = 1
DEBUG: query: update tellers set tbalance = tbalance + 230 where tid = 17
DEBUG: query: update tellers set tbalance = tbalance + 740 where tid = 7
DEBUG: query: update tellers set tbalance = tbalance + 243 where tid = 13
DEBUG: query: select abalance from accounts where aid = 177962
DEBUG: query: update tellers set tbalance = tbalance + 595 where tid = 18
DEBUG: query: update branches set bbalance = bbalance + 595 where bid = 1
DEBUG: query: update tellers set tbalance = tbalance + 252 where tid = 15
I'm trying now is increasing the timeout to 10 times longer. Will
report in next email...
--
Tatsuo Ishii
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
