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

Re: Deadlock condition in driver

From: Richard Evans <richard(dot)evans(at)blueallegro(dot)net>
To: Kris Jurka <books(at)ejurka(dot)com>
Cc: Daniel Migowski <dmigowski(at)ikoffice(dot)de>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Deadlock condition in driver
Date: 2008-05-22 06:34:34
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
We hit this problem and modified the driver to use non-blocking IO to 
fix it.  You lose some of the more unusual features of the driver (such 
as switching the socket after open), but it does fix the blocking.

Richard Evans
> On Wed, 21 May 2008, Daniel Migowski wrote:
>> I came across a deadlock condition in the JDBC driver that rises when 
>> very large queries, containing thousends of statements are send to 
>> the server with statement.execute().
> We already consider this case for batch execution and break the batch 
> into an internal size that we expect is safe from deadlock.  It looks 
> like we should be doing the same for these one query batches.  I'm not 
> sure how tough that will be, but I'll take a look.
> Kris Jurka

In response to


pgsql-bugs by date

Next:From: Kris JurkaDate: 2008-05-22 06:45:41
Subject: Re: Deadlock condition in driver
Previous:From: Thomas HDate: 2008-05-22 03:08:45
Subject: BUG #4186: set lc_messages does not work

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