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 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Rawnsley | 2004-01-30 02:19:23 | Re: Forcing connections closed |
Previous Message | Mark Harrison | 2004-01-30 01:00:27 | hung postmaster when client machine dies? |