Message-ID: <45D0B565.9060402@archonet.com>
Date: Mon, 12 Feb 2007 18:43:49 +0000
From: Richard Huxton <dev@archonet.com>
User-Agent: IceDove 1.5.0.9 (X11/20061220)
MIME-Version: 1.0
To: Ezequias Rodrigues da Rocha <ezequias.rocha@gmail.com>
Cc: Scott Marlowe <smarlowe@g2switchworks.com>,
	pgsql-sql@postgresql.org, pgsql-admin@postgresql.org
Subject: Re: [SQL] Deadlock on transaction
References: <55c095e90702120943v2909044eo91445b0eda3958c7@mail.gmail.com>	
	<1171302488.3565.15.camel@state.g2switchworks.com>
	<55c095e90702121008u6d3d27c0m16e52d63f97c3e7d@mail.gmail.com>
In-Reply-To: <55c095e90702121008u6d3d27c0m16e52d63f97c3e7d@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

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