Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <pgpool-general-owner+archive@lists.postgresql.org>)
	id 1wmZUj-000rGM-1p
	for pgpool-general@arkaria.postgresql.org;
	Wed, 22 Jul 2026 16:08:29 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.96)
	(envelope-from <pgpool-general-owner+archive@lists.postgresql.org>)
	id 1wmZUj-00D5Dl-0o
	for pgpool-general@arkaria.postgresql.org;
	Wed, 22 Jul 2026 16:08:28 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.96)
	(envelope-from <a.mantzios@cloud.gatewaynet.com>)
	id 1wmZUj-00D5Da-0G
	for pgpool-general@lists.postgresql.org;
	Wed, 22 Jul 2026 16:08:28 +0000
Received: from cloud.gatewaynet.com ([185.90.37.94])
	by makus.postgresql.org with esmtps  (TLS1.2) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.98.2)
	(envelope-from <a.mantzios@cloud.gatewaynet.com>)
	id 1wmZUe-00000001RW1-0SRK
	for pgpool-general@lists.postgresql.org;
	Wed, 22 Jul 2026 16:08:27 +0000
Content-Type: multipart/alternative;
 boundary="------------Rg9wHYXEY9iGPEqxu2a2yRjV"
Message-ID: <754bc89e-abab-43a9-bf7e-1b3acf73d931@cloud.gatewaynet.com>
Date: Wed, 22 Jul 2026 19:08:19 +0300
MIME-Version: 1.0
Subject: Re: low level protocol, implicit transactions , "idle in transaction"
 issue
To: pgpool-general@lists.postgresql.org
References: <25939319-d77c-4df9-9e65-dfb1637ccd33@cloud.gatewaynet.com>
Content-Language: en-US
From: Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>
In-Reply-To: <25939319-d77c-4df9-9e65-dfb1637ccd33@cloud.gatewaynet.com>
List-Id: <pgpool-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgpool-general@lists.postgresql.org>
List-Owner: <mailto:pgpool-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgpool-general>
Archived-At: 
 <https://www.postgresql.org/message-id/754bc89e-abab-43a9-bf7e-1b3acf73d931%40cloud.gatewaynet.com>
Precedence: bulk

This is a multi-part message in MIME format.
--------------Rg9wHYXEY9iGPEqxu2a2yRjV
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

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!
>
--------------Rg9wHYXEY9iGPEqxu2a2yRjV
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>sorry I forgot to mention,</p>
    <p>before the patch, disabling the query cache in pgpool the problem
      went away.</p>
    <div class="moz-cite-prefix">On 7/22/26 17:32, Achilleas Mantzios
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:25939319-d77c-4df9-9e65-dfb1637ccd33@cloud.gatewaynet.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <p>Dear pgpool team</p>
      <p>This is our setup :</p>
      <p>Quarkus (Agroal) -&gt;  <span
          style="color:#000000;background-color:#ffffff;">pgbouncer-1.25.1
          -&gt; pgpool </span>4.7.2 -&gt; pgsql 18.3</p>
      <p>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 -&gt;
        pgsql.</p>
      <p>Bypassing pgpool, i.e. pgbouncer -&gt; directly to pgsql , the
        issue was not there.</p>
      <p>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  <span
          style="font-family:monospace"><span
            style="color:#000000;background-color:#ffffff;">GLM-5.2-NVFP4</span></span> )
        from within pgpool 4.7.2 code base and try to see what's going
        on. </p>
      <p>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.</p>
      <p>The problem seems gone .</p>
      <p>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.</p>
      <p>Thank you!</p>
    </blockquote>
  </body>
</html>

--------------Rg9wHYXEY9iGPEqxu2a2yRjV--