| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Daniel Migowski <dmigowski(at)ikoffice(dot)de> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, Richard Evans <richard(dot)evans(at)blueallegro(dot)net> |
| Subject: | Re: Deadlock condition in driver |
| Date: | 2008-10-18 13:51:40 |
| Message-ID: | Pine.BSO.4.64.0810180948370.26386@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martin Gregorie | 2008-10-18 22:57:39 | Problem with the pg_dumpall file format |
| Previous Message | Kris Jurka | 2008-10-17 19:06:53 | Re: BUG #4483: setAutoCommit false shouldn't be necessary for fetchSize to work |