Re: share lock error - Mailing list pgsql-general

From Tom Lane
Subject Re: share lock error
Date
Msg-id 4871.1160086256@sss.pgh.pa.us
Whole thread Raw
In response to share lock error  (Terry Fielder <terry@ashtonwoodshomes.com>)
Responses Re: share lock error  (Terry Fielder <terry@ashtonwoodshomes.com>)
List pgsql-general
Terry Fielder <terry@ashtonwoodshomes.com> writes:
> I am getting this in my log file:
> 2006-10-05 16:06:23 [6469] ERROR:  deadlock detected
> DETAIL:  Process 6469 waits for ShareLock on transaction 668582701;
> blocked by process 28763.
>         Process 28763 waits for ShareLock on transaction 668586325;
> blocked by process 6469.

> I believe that the elements "a" and "b" are different tables.

Actually, what you're looking at there is a conflict on row-level locks
being obtained in opposite orders.  What PG version is this?  If it's
8.1 you can identify the row in question from other entries in pg_locks,
but if it's older then there's no easy way to find out.

            regards, tom lane

pgsql-general by date:

Previous
From: Erik Jones
Date:
Subject: Re: share lock error
Next
From: "Guy Rouillier"
Date:
Subject: Re: Storing images in PostgreSQL databases (again)