From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Kevin Wooten <kdubb(at)me(dot)com> |
Cc: | "Vinay S (vinas)" <vinas(at)cisco(dot)com>, Dave Cramer <davecramer(at)gmail(dot)com>, List <pgsql-jdbc(at)postgresql(dot)org> |
Subject: | Re: JDBC executeBatch() hangs without error |
Date: | 2013-09-26 17:48:03 |
Message-ID: | alpine.BSO.2.03.1309261345001.26217@ejurka.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On Thu, 26 Sep 2013, Kevin Wooten wrote:
> Could this be related to the note in QueryExecutorImpl.java ~ line 287
> titled "Deadlock Avoidance"?
> If I remember correctly it's specifically related to batched queries and
> synchronous TCP.
Almost certainly. The thing to look at is setting the network buffer
sizes to use to large values to avoid the deadlock. The default values
are machine dependent which also explains it working or not on different
machines. These are unfortunately not documented, but were introduced in
this commit:
https://github.com/pgjdbc/pgjdbc/commit/4e7f65b91e95d6249c78de6944f09cd34ef1ae87
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Vinay S (vinas) | 2013-09-26 17:49:44 | Re: JDBC executeBatch() hangs without error |
Previous Message | Kevin Wooten | 2013-09-26 17:40:49 | Re: JDBC executeBatch() hangs without error |