Re: share lock error - Mailing list pgsql-general

From Terry Fielder
Subject Re: share lock error
Date
Msg-id 4525C202.6040601@ashtonwoodshomes.com
Whole thread Raw
In response to Re: share lock error  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: share lock error
List pgsql-general
7.4.3

And the records are gone from pg_locks, how much time after the deadlock do I have before they are purged?


Terry Fielder
terry@greatgulfhomes.com
Associate Director Software Development and Deployment
Great Gulf Homes / Ashton Woods Homes
Fax: (416) 441-9085


Tom Lane wrote:
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

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings
 

pgsql-general by date:

Previous
From: Ron Johnson
Date:
Subject: Re: Storing images in PostgreSQL databases (again)
Next
From: "Gregory S. Williamson"
Date:
Subject: Re: Storing images in PostgreSQL databases (again)