| 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 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-02-12 21:31:24 | Re: pid file problem |
| Previous Message | Richard Huxton | 2007-02-12 19:50:49 | Re: [SQL] Deadlock on transaction |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Midgley | 2007-02-12 20:24:13 | Re: COPY FROM query |
| Previous Message | Richard Huxton | 2007-02-12 19:50:49 | Re: [SQL] Deadlock on transaction |