From: Tom Lane <tgl@sss.pgh.pa.us>
To: Marc G. Fournier <scrappy@postgresql.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: Frequent 'deadlock detected' in 7.4 ... or just my bad code?
Date: Mon, 05 Apr 2004 11:13:54 -0400
Message-ID: <11570.1081178034@sss.pgh.pa.us> (raw)
In-Reply-To: <20040405114031.N79409@ganymede.hub.org>
References: <20040405114031.N79409@ganymede.hub.org>
"Marc G. Fournier" <scrappy@postgresql.org> writes:
> Now, the scripts are wrap'd in a BEGIN/END ... if a file fails to be
> loaded, I want the whole thing to rollback ... the deadlock itself, I'm
> presuming, is because two servers are trying to update the same
> $ip_id/$port/$company_id record, at the same time ...
Actually, the problem is more likely that two servers try to update two
different rows in opposite orders. It's not possible to deadlock when
only one lock is involved.
You could work around this by ensuring that all sessions update rows in
a consistent order; for instance, at the beginning of a transaction sort
your intended updates by primary key and then apply in that order.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, scrappy@postgresql.org
Subject: Re: Frequent 'deadlock detected' in 7.4 ... or just my bad code?
In-Reply-To: <11570.1081178034@sss.pgh.pa.us>
References: <20040405114031.N79409@ganymede.hub.org> <11570.1081178034@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox