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>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: INSERT deadlocks (bug or feature?)
Date: 2005-05-27 14:15:32
Message-ID: 14459.1117203332@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message fremaux 2005-05-27 14:36:43 BUG #1684: ERROR: Relation 17065 does not exist
Previous Message evgeny gridasov 2005-05-27 10:06:07 INSERT deadlocks (bug or feature?)