pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: papegaaij (@papegaaij) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #3724: Regression: FATAL: simple query "BEGIN" arrived before ending an extended query message
Date: Wed, 09 Jul 2025 10:53:15 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
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?
view thread (9+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] issue #3724: Regression: FATAL: simple query "BEGIN" arrived before ending an extended query message
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox