From: Richard Huxton <dev@archonet.com>
To: Ezequias Rodrigues da Rocha <ezequias.rocha@gmail.com>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-admin@postgresql.org
Subject: Re: [SQL] Deadlock on transaction
Date: Mon, 12 Feb 2007 18:43:49 +0000
Message-ID: <45D0B565.9060402@archonet.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>
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 ?
PG has quite good concurrency behaviour. And "can't access the database"
isn't anything to do with locking - clients should still be able to log in.
We'll need more details:
1. How do you know this is a deadlock? You haven't shown us what's in
pg_locks, but I assume you've identified the problem there.
2. What data are you loading, to what tables?
3. Are there any foreign-keys or triggers we would need to know about?
--
Richard Huxton
Archonet Ltd
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: dev@archonet.com, ezequias.rocha@gmail.com, smarlowe@g2switchworks.com, pgsql-admin@postgresql.org
Subject: Re: [SQL] Deadlock on transaction
In-Reply-To: <45D0B565.9060402@archonet.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