From: Stephan Szabo <sszabo@megazone.bigpanda.com>
To: Gaetano Mendola <mendola@bigfoot.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: commit after dead lock
Date: Thu, 29 Jan 2004 17:11:07 -0800 (PST)
Message-ID: <20040129170739.U35951@megazone.bigpanda.com> (raw)
In-Reply-To: <4019A484.5010509@bigfoot.com>
References: <4019A484.5010509@bigfoot.com>
On Fri, 30 Jan 2004, Gaetano Mendola wrote:
> Hi all,
> is it normal that postgres dont complain
> doing a commit after a deadlock ?
>
> kalman=# select * from test where a = 5 for update;
> ERROR: deadlock detected
> DETAIL: Process 4144 waits for ShareLock on transaction 40180; blocked
> by process 4141.
> Process 4141 waits for ShareLock on transaction 40181; blocked by
> process 4144.
> kalman=# commit;
> COMMIT
It's not really any different than other errors. The commit doesn't
complain (although it also doesn't actually commit anything).
sszabo=# begin;
BEGIN
sszabo=# select * from foo;
ERROR: relation "foo" does not exist
sszabo=# commit;
COMMIT
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: sszabo@megazone.bigpanda.com, mendola@bigfoot.com
Subject: Re: commit after dead lock
In-Reply-To: <20040129170739.U35951@megazone.bigpanda.com>
References: <4019A484.5010509@bigfoot.com> <20040129170739.U35951@megazone.bigpanda.com>
* 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