Message-ID: <gh-pgjdbc-pgjdbc-194-c57627689@github.com>
From: "ringerc (@ringerc)" <noreply+ringerc@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 02 Oct 2014 13:16:57 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #194: PgJDBC can experience client/server deadlocks during batch execution
In-Reply-To: <gh-pgjdbc-pgjdbc-194@github.com>
References: <gh-pgjdbc-pgjdbc-194@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: ringerc
X-GitHub-Comment-Id: 57627689
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 194
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/194#issuecomment-57627689
Content-Type: text/plain; charset=utf-8

To reduce the likeihood of tripping this bug, PgJDBC doesn't queue batches that return result sets, such as a `PreparedStatement` that requests generated keys, per issue #195.

One possible option for making deadlocks impossible is covered in brief by issue #163 - using non-blocking sockets with java.nio. However, it's likely to be intrusive.