From: | Terry Fielder <terry(at)ashtonwoodshomes(dot)com> |
---|---|
To: | |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: share lock error |
Date: | 2006-10-06 02:40:02 |
Message-ID: | 4525C202.6040601@ashtonwoodshomes.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)greatgulfhomes(dot)com
Associate Director Software Development and Deployment
Great Gulf Homes / Ashton Woods Homes
Fax: (416) 441-9085
Tom Lane wrote:
> Terry Fielder <terry(at)ashtonwoodshomes(dot)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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory S. Williamson | 2006-10-06 04:22:04 | Re: Storing images in PostgreSQL databases (again) |
Previous Message | Leonel Nunez | 2006-10-06 01:56:05 | Re: Storing images in PostgreSQL databases (again) |