Re: Pgsql jdbc driver 8.3 Build 603: Commit deadlock - Mailing list pgsql-jdbc

From Oliver Jowett
Subject Re: Pgsql jdbc driver 8.3 Build 603: Commit deadlock
Date
Msg-id 4918E3DC.7080801@opencloud.com
Whole thread Raw
In response to Re: Pgsql jdbc driver 8.3 Build 603: Commit deadlock  (Kris Jurka <books@ejurka.com>)
Responses Re: Pgsql jdbc driver 8.3 Build 603: Commit deadlock  ("Shawn Chasse" <shawnchasse@gmail.com>)
List pgsql-jdbc
Kris Jurka wrote:
>
>
> On Tue, 11 Nov 2008, Oliver Jowett wrote:
>
>> Shawn Chasse wrote:
>>>
>>> Recently I have run into a problem where a commit call in my java
>>> code will propogate down to the driver and eventually deadlock
>>> waiting for a response.
>>
>> While your top-level code may be calling commit() on a Hibernate API,
>> the actual JDBC work that is going on doesn't involve a commit - it
>> looks like a batch insert to me.
>
> It could be another example of this deadlock:
>
> http://archives.postgresql.org/pgsql-jdbc/2008-10/msg00045.php

Hmm, but shouldn't that manifest as the driver blocking on a socket write?

In Shawn's case we're blocking on read.

-O

pgsql-jdbc by date:

Previous
From: Tiago Alves
Date:
Subject: Using SELECT IN with prepared statement
Next
From: Alexander Panzhin
Date:
Subject: Re: Using SELECT IN with prepared statement