| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Daniel Migowski <dmigowski(at)ikoffice(dot)de>, PostgreSQL - JDBC <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: Deadlock detection |
| Date: | 2009-01-22 02:13:53 |
| Message-ID: | 4977D661.6050007@opencloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Simon Riggs wrote:
> There was another hang earlier today. One session just went idle in
> transaction on server right in the middle of a long transaction. 1500
> statements in about a second on the session, then nothing, while holding
> locks. People are adamant it is not the application; much checking has
> been done.
It's worth noting that this does not sound like the socket deadlock case.
In the socket deadlock case, the backend will be stuck in PARSE or
something similar, blocked trying to write to the JDBC client.
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrea Lombardoni | 2009-01-22 14:24:35 | PostgreSQL JDBC - Long Running Stored Procedure - Out of Memory |
| Previous Message | Oliver Jowett | 2009-01-22 02:03:08 | Re: Deadlock detection |