Re: BUG #4648: needless deadlock on tables having foreign-key

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Konstantin <kostya2702(at)rambler(dot)ru>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #4648: needless deadlock on tables having foreign-key
Date: 2009-02-13 00:10:34
Message-ID: 19543.1234483834@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Konstantin <kostya2702(at)rambler(dot)ru> writes:
> I just want to emphasize that mentioned implementation artifact born not
> obvious issues at applications side.

[ shrug... ] The "implementation artifact" is that you didn't get a
deadlock *earlier*. You can't expect to update referenced rows and
referencing rows in the same transaction and not risk deadlock against
other transactions doing the same thing.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Scott Carey 2009-02-13 05:53:45 8.3.5: Query Planner takes 15+ seconds to plan Update or Delete queries on partitioned tables.
Previous Message Konstantin 2009-02-12 23:31:06 Re: BUG #4648: needless deadlock on tables having foreign-key