DEADLOCK INSERT

From: "Ricardo Durao" <durao(at)pcsolution(dot)com(dot)br>
To: <pgsql-admin(at)postgresql(dot)org>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: DEADLOCK INSERT
Date: 2005-06-15 03:16:10
Message-ID: 002601c57158$9432b8e0$933311c9@starwarkzed40f
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin


Hello,

Tom Lane

I am using version 7.4.8 and I think that I have this problem(bug) that is
describe here for you.

_________________________________________________________________________

Re: INSERT deadlocks (bug or feature?)

From: Tom Lane <tgl ( at ) sss ( dot ) pgh ( dot ) pa ( dot ) us>
To: evgeny gridasov <eugrid ( at ) fpm ( dot ) kubsu ( dot ) ru>
Subject: Re: INSERT deadlocks (bug or feature?)
Date: Fri, 27 May 2005 10:15:32 -0400

evgeny gridasov <eugrid ( at ) fpm ( dot ) kubsu ( dot ) ru> writes:
> ... and we recieve a deadlock!
> Easy to understand why: each insert statement generates query like:
> SELECT 1 FROM ONLY "public"."ref" x WHERE "id" = $1 FOR UPDATE OF x
> So, is this behaviour of postgresql is a bug or feature?

An extremely well-known bug ... which is fixed in CVS tip.

regards, tom lane

_________________________________________________________________________

How I can fix this in my version. Have a Pacth ? I can get the source of the
file and re-compile the Postgresql ?

Thanks, for any Help.

Ricardo Durão

"

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.7.2/14 - Release Date: 14/6/2005

Browse pgsql-admin by date

  From Date Subject
Next Message Tom Lane 2005-06-15 03:22:34 Re: Connecting via localhost pg-8.0.3
Previous Message Amrit Angsusingh 2005-06-15 03:00:13 Blob error after backup and restore [database > 5.5 Gb.]