Skip site navigation (1) Skip section navigation (2)

Re: commit after dead lock

From: Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com>
To: Gaetano Mendola <mendola(at)bigfoot(dot)com>
Cc: "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: commit after dead lock
Date: 2004-01-30 01:11:07
Message-ID: 20040129170739.U35951@megazone.bigpanda.com (view raw or flat)
Thread:
Lists: pgsql-admin
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


In response to

Responses

pgsql-admin by date

Next:From: Andrew RawnsleyDate: 2004-01-30 02:19:23
Subject: Re: Forcing connections closed
Previous:From: Mark HarrisonDate: 2004-01-30 01:00:27
Subject: hung postmaster when client machine dies?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group