Message-ID: <gh-pgjdbc-pgjdbc-194-c2164009671@github.com>
From: "ringerc (@ringerc)" <noreply+ringerc@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 12 Jun 2024 22:35:25 +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: 2164009671
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-2164009671
Content-Type: text/plain; charset=utf-8

The only true fix for this issue is to re-architect PgJDBC so it uses separate reader and writer threads on the socket, or uses non-blocking I/O for all sockets including SSL.

Anything else is just a workaround that guesstimates the safe batch size.