| From: | Achilleas Mantzios <a(dot)mantzios(at)cloud(dot)gatewaynet(dot)com> |
|---|---|
| To: | "pgpool-general(at)lists(dot)postgresql(dot)org" <pgpool-general(at)lists(dot)postgresql(dot)org> |
| Cc: | Achilleas Mantzios <itdev(at)gatewaynet(dot)com> |
| Subject: | low level protocol, implicit transactions , "idle in transaction" issue |
| Date: | 2026-07-22 14:32:55 |
| Message-ID: | 25939319-d77c-4df9-9e65-dfb1637ccd33@cloud.gatewaynet.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgpool-general |
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!
| Attachment | Content-Type | Size |
|---|---|---|
| do_query_sync.patch | text/x-patch | 2.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleas Mantzios | 2026-07-22 16:08:19 | Re: low level protocol, implicit transactions , "idle in transaction" issue |
| Previous Message | Koshino Taiki | 2026-06-04 10:06:38 | Pgpool-II 4.7.2, 4.6.7, 4.5.12, 4.4.17 and 4.3.20 officially released |