| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Terry Fielder <terry(at)ashtonwoodshomes(dot)com> |
| Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: share lock error |
| Date: | 2006-10-05 22:10:56 |
| Message-ID: | 4871.1160086256@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Guy Rouillier | 2006-10-05 22:12:29 | Re: Storing images in PostgreSQL databases (again) |
| Previous Message | Erik Jones | 2006-10-05 21:32:21 | Re: share lock error |