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

Re: [SQL] Deadlock on transaction

From: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>
To: Ezequias Rodrigues da Rocha <ezequias(dot)rocha(at)gmail(dot)com>
Cc: Richard Huxton <dev(at)archonet(dot)com>, pgsql-admin(at)postgresql(dot)org
Subject: Re: [SQL] Deadlock on transaction
Date: 2007-02-12 19:56:30
Message-ID: 1171310190.3565.22.camel@state.g2switchworks.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-sql
On Mon, 2007-02-12 at 13:20, Ezequias Rodrigues da Rocha wrote:
> This is delphi. I don't intent you understand but the sql actions are
> quite simple (I am reading a list of numbers).

Hmmm.  I'm not seeing anything in your example that should be blocking
other transactions.  Is there anything that Delphi is doing here that we
don't see from your code?  I.e. does to toss a "for update" on the ends
of selects, or "lock table" in there we don't see?

Maybe you could turn on logging of ALL queries in the database and see
what's really going on there, cause I'm not seeing anything in your code
to point to blocking.

In response to

pgsql-admin by date

Next:From: Tom LaneDate: 2007-02-12 21:31:24
Subject: Re: pid file problem
Previous:From: Richard HuxtonDate: 2007-02-12 19:50:49
Subject: Re: [SQL] Deadlock on transaction

pgsql-sql by date

Next:From: Steve MidgleyDate: 2007-02-12 20:24:13
Subject: Re: COPY FROM query
Previous:From: Richard HuxtonDate: 2007-02-12 19:50:49
Subject: Re: [SQL] Deadlock on transaction

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