Re: [SQL] Deadlock on transaction - Mailing list pgsql-admin

From Ezequias Rodrigues da Rocha
Subject Re: [SQL] Deadlock on transaction
Date
Msg-id 55c095e90702121047x1c66b098xbcf0d308195ff584@mail.gmail.com
Whole thread Raw
In response to Re: [SQL] Deadlock on transaction  (Richard Huxton <dev@archonet.com>)
Responses Re: [SQL] Deadlock on transaction  (Richard Huxton <dev@archonet.com>)
List pgsql-admin


2007/2/12, Richard Huxton <dev@archonet.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.

I knew becouse my Delphi application reports it to me. If there is anything in pg_log I could see it to you.

2. What data are you loading, to what tables?

Simple data but allways with the same username (does it make any difference ?)

3. Are there any foreign-keys or triggers we would need to know about?

No.

Ps: When I do not use transactions the connections does not lock to other users.
--
   Richard Huxton
   Archonet Ltd



--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
                                  Atenciosamente (Sincerely)
                        Ezequias Rodrigues da Rocha
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
A pior das democracias ainda é melhor do que a melhor das ditaduras
The worst of democracies is still better than the better of dictatorships
http://ezequiasrocha.blogspot.com/

pgsql-admin by date:

Previous
From: teknokrat
Date:
Subject: Re: pg on windows server 2003 64 bit edition
Next
From: "Peter Kovacs"
Date:
Subject: pid file problem