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
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
