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

Re: Pgsql jdbc driver 8.3 Build 603: Commit deadlock

From: Oliver Jowett <oliver(at)opencloud(dot)com>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Shawn Chasse <shawnchasse(at)gmail(dot)com>, pgsql-jdbc(at)postgresql(dot)org
Subject: Re: Pgsql jdbc driver 8.3 Build 603: Commit deadlock
Date: 2008-11-11 01:46:04
Message-ID: 4918E3DC.7080801@opencloud.com (view raw or flat)
Thread:
Lists: 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

In response to

Responses

pgsql-jdbc by date

Next:From: Ingmar LötzschDate: 2008-11-11 07:38:38
Subject: Re: Using SELECT IN with prepared statement
Previous:From: Kris JurkaDate: 2008-11-11 00:31:42
Subject: Re: Pgsql jdbc driver 8.3 Build 603: Commit deadlock

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