From: Scott Marlowe <smarlowe@g2switchworks.com>
To: Ezequias Rodrigues da Rocha <ezequias.rocha@gmail.com>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-admin@postgresql.org
Subject: Re: Deadlock on transaction
Date: Mon, 12 Feb 2007 13:20:51 -0600
Message-ID: <1171308051.3565.18.camel@state.g2switchworks.com> (raw)
In-Reply-To: <55c095e90702121008u6d3d27c0m16e52d63f97c3e7d@mail.gmail.com>
References: <55c095e90702120943v2909044eo91445b0eda3958c7@mail.gmail.com>
<1171302488.3565.15.camel@state.g2switchworks.com>
<55c095e90702121008u6d3d27c0m16e52d63f97c3e7d@mail.gmail.com>
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?
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 using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: smarlowe@g2switchworks.com, ezequias.rocha@gmail.com, pgsql-admin@postgresql.org
Subject: Re: Deadlock on transaction
In-Reply-To: <1171308051.3565.18.camel@state.g2switchworks.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