pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gaetano Mendola <mendola@bigfoot.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: commit after dead lock
Date: Fri, 30 Jan 2004 01:25:40 +0100
Message-ID: <4019A484.5010509@bigfoot.com> (raw)

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
kalman=#


Regards
Gaetano Mendola




view thread (4+ messages)  latest in thread

Message-ID: <4019A484.5010509@bigfoot.com>
Permalink:  ../4019A484.5010509@bigfoot.com/
Also on:    postgresql.org/message-id/4019A484.5010509@bigfoot.com

 · 

reply

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: mendola@bigfoot.com
  Subject: Re: commit after dead lock
  In-Reply-To: <4019A484.5010509@bigfoot.com>
  References: <4019A484.5010509@bigfoot.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