Re: Deadlock condition in driver - Mailing list pgsql-bugs

From Kris Jurka
Subject Re: Deadlock condition in driver
Date
Msg-id Pine.BSO.4.64.0810180948370.26386@leary.csoft.net
Whole thread Raw
In response to Re: Deadlock condition in driver  (Kris Jurka <books@ejurka.com>)
List pgsql-bugs
On Wed, 21 May 2008, Kris Jurka wrote:

> 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.

I've committed a fix to CVS for this problem, and it should fix your case,
but will not fix all deadlocks as a move to NIO or threading would.

For more details, see:

http://archives.postgresql.org/pgsql-jdbc/2008-10/msg00034.php

Kris Jurka

pgsql-bugs by date:

Previous
From: Kris Jurka
Date:
Subject: Re: BUG #4483: setAutoCommit false shouldn't be necessary for fetchSize to work
Next
From: hubert depesz lubaczewski
Date:
Subject: ftp server symlink