From: | "Francesco Formenti - TVBLOB S(dot)r(dot)l(dot)" <francesco(dot)formenti(at)tvblob(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | deadlock on the same relation |
Date: | 2005-12-02 10:51:35 |
Message-ID: | 43902737.8070404@tvblob.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi all,
I have a problem about deadlock. I have several stored procedures; only
one of them uses ACCESS EXCLUSIVE LOCK on a table; however, all the
stored procedures can access to that table, using SELECT, INSERT or UPDATE.
The stored procedures are called by different processes of an external
application.
In a non-predictable way, I obtain error messages like this one:
2005-11-29 18:23:06 [12771] ERROR: deadlock detected
DETAIL: Process 12771 waits for AccessExclusiveLock on relation 26052
of database 17142; blocked by process 12773.
Process 12773 waits for AccessExclusiveLock on relation 26052 of
database 17142; blocked by process 12771.
CONTEXT: PL/pgSQL function "set_session_box_status" line 7 at SQL statement
I don't understand what's happening; is it possible that a deadlock is
detected on the same relation (that is, the stored procedure using the
ACCESS EXCLUSIVE LOCK mentioned before) ?
I'm using Postgres 7.4.7 on a Debian Sarge.
Thanks!
Francesco
--
Francesco Formenti - TVBLOB S.r.l.
Software Engineer
Via G. Paisiello, 9 20131 Milano, Italia
-----------------------------------------
Phone +39 02 36562440
Fax +39 02 20408347
Web Site http://www.tvblob.com
E-mail francesco(dot)formenti(at)tvblob(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Volkan YAZICI | 2005-12-02 11:55:41 | Re: encoding problem |
Previous Message | Richard Huxton | 2005-12-02 09:14:52 | Re: postmaster / resolv.conf / dns problem |