Message-ID: <gh-pgjdbc-pgjdbc-3724-c3052179009@github.com>
From: "papegaaij (@papegaaij)" <noreply+papegaaij@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 09 Jul 2025 10:53:15 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3724: Regression: FATAL:  simple query "BEGIN" arrived before ending an extended query message
In-Reply-To: <gh-pgjdbc-pgjdbc-3724@github.com>
References: <gh-pgjdbc-pgjdbc-3724@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: papegaaij
X-GitHub-Comment-Id: 3052179009
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3724
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3724#issuecomment-3052179009
Content-Type: text/plain; charset=utf-8

That does make sense indeed. However, this change now makes it virtually impossible to upgrade PgJDBC for everyone using pgpool-II. The discussion linked in #3107 did not come to a conclusion and the ticket has not seen any activity since it was created. What do you think is the way forward? We cannot stay on 42.7.5 indefinitely nor can we stop using pgpool-II. Do you think this should be addressed in pgpool-II or will this be fixed in an upcoming version of PgJDBC?