MIME-Version: 1.0
From: Emond Papegaaij <emond.papegaaij@gmail.com>
Date: Wed, 9 Jul 2025 13:13:26 +0200
Message-ID: 
 <CAGXsc+YizFbO1kOhnNq_oRz9F2iDtjCGGq0oNA+BjcQPqJy8tg@mail.gmail.com>
Subject: FATAL: simple query "BEGIN" arrived before ending an extended query
 message
To: pgpool-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000001f419306397d2bfb"
Archived-At: 
 <https://www.postgresql.org/message-id/CAGXsc%2BYizFbO1kOhnNq_oRz9F2iDtjCGGq0oNA%2BBjcQPqJy8tg%40mail.gmail.com>
Precedence: bulk

--0000000000001f419306397d2bfb
Content-Type: text/plain; charset="UTF-8"

Hi all,

Recently we started seeing errors from pgpool-II stating 'FATAL: simple
query "BEGIN" arrived before ending an extended query message'. These
errors started occurring after upgrading PgJDBC from 42.7.5 to 42.7.7. I've
created the following ticket at PgJDBC:
https://github.com/pgjdbc/pgjdbc/issues/3724 . It was closed as a duplicate
of https://github.com/pgjdbc/pgjdbc/issues/3107 , which describes a similar
issue and was opened by Tatsuo Ishii.

The problem however, is that previously the error was only triggered when
using autosave, which is not a common setup, but now the error is triggered
even when using default configuration. This makes it impossible to combine
PgJDBC 42.7.6 and up with pgpool-II. I do not know what the plans are on
this from the side of PostgreSQL and PgJDBC, but I just wanted to raise
some awareness on this issue here. IMHO PostgreSQL should either explicitly
allow this (in which case pgpool-II needs to be fixed) or explicitly
disallow it (in which case PgJDBC needs to be fixed). The current situation
is no good as we now simply cannot upgrade PgJDBC anymore (and the same
will be true for all other users of pgpool-II).

Best regards,
Emond Papegaaij

--0000000000001f419306397d2bfb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<br><br>Recently we started seeing errors from pgpo=
ol-II stating &#39;FATAL: simple query &quot;BEGIN&quot; arrived before end=
ing an extended query message&#39;. These errors started occurring after up=
grading PgJDBC from 42.7.5 to 42.7.7. I&#39;ve created the following ticket=
 at PgJDBC: <a href=3D"https://github.com/pgjdbc/pgjdbc/issues/3724">https:=
//github.com/pgjdbc/pgjdbc/issues/3724</a> . It was closed as a duplicate o=
f <a href=3D"https://github.com/pgjdbc/pgjdbc/issues/3107">https://github.c=
om/pgjdbc/pgjdbc/issues/3107</a> , which describes a similar issue and was =
opened by Tatsuo Ishii.<br><br>The problem however, is that previously the =
error was only triggered when using autosave, which is not a common setup, =
but now the error is triggered even when using default configuration. This =
makes it impossible to combine PgJDBC 42.7.6 and up with pgpool-II. I do no=
t know what the plans are on this from the side of PostgreSQL and PgJDBC, b=
ut I just wanted to raise some awareness on this issue here. IMHO PostgreSQ=
L should either explicitly allow this (in which case pgpool-II needs to be =
fixed) or explicitly disallow it (in which case PgJDBC needs to be fixed). =
The current situation is no good as we now simply cannot upgrade PgJDBC any=
more (and the same will be true for all other users of pgpool-II).<br><br>B=
est regards,<br>Emond Papegaaij</div>

--0000000000001f419306397d2bfb--