From: Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>
To: pgpool-general@lists.postgresql.org
Subject: Re: low level protocol, implicit transactions , "idle in transaction" issue
Date: Wed, 22 Jul 2026 19:08:19 +0300
Message-ID: <754bc89e-abab-43a9-bf7e-1b3acf73d931@cloud.gatewaynet.com> (raw)
In-Reply-To: <25939319-d77c-4df9-9e65-dfb1637ccd33@cloud.gatewaynet.com>
References: <25939319-d77c-4df9-9e65-dfb1637ccd33@cloud.gatewaynet.com>
sorry I forgot to mention,
before the patch, disabling the query cache in pgpool the problem went away.
On 7/22/26 17:32, Achilleas Mantzios wrote:
>
> Dear pgpool team
>
> This is our setup :
>
> Quarkus (Agroal) -> pgbouncer-1.25.1 -> pgpool 4.7.2 -> pgsql 18.3
>
> We noticed that with no explicit transactions, at start up SQL queries
> (application_name, search_path, etc), we experienced random 'idle in
> transaction' connections from pgpool -> pgsql.
>
> Bypassing pgpool, i.e. pgbouncer -> directly to pgsql , the issue was
> not there.
>
> So, bypassing the past excellent relation and collaboration I had with
> you guys, I got into the temptation to use our local AI cli agent
> (against our local GLM-5.2-NVFP4 ) from within pgpool 4.7.2 code base
> and try to see what's going on.
>
> So it gave it a thorough examination, looked at past issues, etc and
> it came up with a patch. It applied the patch , compiled and
> installed, and I only had to restart pgpool.
>
> The problem seems gone .
>
> I attach the patch. Please review and tell me your thoughts. I Know I
> should maybe go the classic route, mailing list, advice from you, full
> logging, etc till I demo the issue, but the time is pushing us hard.
>
> Thank you!
>
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: pgpool-general@postgresql.org
Cc: a.mantzios@cloud.gatewaynet.com, pgpool-general@lists.postgresql.org
Subject: Re: low level protocol, implicit transactions , "idle in transaction" issue
In-Reply-To: <754bc89e-abab-43a9-bf7e-1b3acf73d931@cloud.gatewaynet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox