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

Re: Deadlock on transaction

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
To: Ezequias Rodrigues da Rocha <ezequias(dot)rocha(at)gmail(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org, pgsql-admin(at)postgresql(dot)org
Subject: Re: Deadlock on transaction
Date: 2007-02-12 19:20:51
Message-ID: 1171308051.3565.18.camel@state.g2switchworks.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-sql
On Mon, 2007-02-12 at 12:08, Ezequias Rodrigues da Rocha wrote:
> I mean really deadlock. Other transactions can't access the database
> until the main transaction is complete. A question:
> 
> PostgreSQL doesn't permit multiple transactions concurrently ?

Again, that's not a deadlock.  A deadlock would mean that the
transaction causing the lock never returned, because it wound up waiting
for another transaction that was in turn waiting on it.  i.e.

begin transaction a
begin trasnaction b
a does something that waits on b
b does something that waits on a
neither transaction can complete.

What you have is a blocking transaction.

In postgresql, very few transactions tend to block other transactions.

Have you got a test case that demonstrates your problem with blocking?


In response to

pgsql-admin by date

Next:From: Ezequias Rodrigues da RochaDate: 2007-02-12 19:27:15
Subject: Re: [ADMIN] Deadlock on transaction
Previous:From: Ezequias Rodrigues da RochaDate: 2007-02-12 19:20:30
Subject: Re: [SQL] Deadlock on transaction

pgsql-sql by date

Next:From: Ezequias Rodrigues da RochaDate: 2007-02-12 19:27:15
Subject: Re: [ADMIN] Deadlock on transaction
Previous:From: Ezequias Rodrigues da RochaDate: 2007-02-12 19:20:30
Subject: Re: [SQL] Deadlock on transaction

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