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.94.2) (envelope-from ) id 1t1jxH-0007zy-82 for pgsql-admin@arkaria.postgresql.org; Fri, 18 Oct 2024 10:11:35 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t1jxF-001yKr-Ja for pgsql-admin@arkaria.postgresql.org; Fri, 18 Oct 2024 10:11:33 +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.94.2) (envelope-from ) id 1t1jxF-001yKj-8S for pgsql-admin@lists.postgresql.org; Fri, 18 Oct 2024 10:11:33 +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.94.2) (envelope-from ) id 1t1jxC-001WF9-Tj for pgsql-admin@lists.postgresql.org; Fri, 18 Oct 2024 10:11:32 +0000 Content-Type: multipart/alternative; boundary="------------G0u98XYsz0tRoo0S0RdZsn6b" Message-ID: Date: Fri, 18 Oct 2024 11:11:28 +0100 MIME-Version: 1.0 From: Achilleas Mantzios - cloud Subject: Migrating from 10 -> 16, PreparedStatements disabled in JDBC and pgbouncer, I am getting : bind /C_5 To: pgsql-admin@lists.postgresql.org Cc: Achilleas Mantzios Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------G0u98XYsz0tRoo0S0RdZsn6b Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi All We have disabled prepared statements in the JDBC settings (prepareThreshold=0) and in pgbouncer (max_prepared_statements=0). I have noticed in the pgsql 16.4 logs some lines with this pattern : 10.9.0.110(45201) [4079203] 67122b3b.3e3e63 2024-10-18 12:32:44.260 EEST SMA amantzio@dynacom line:35 LOG: duration: 0.166 ms parse : SELECT work_status FROM company_stuff WHERE ldap_cn = $ 1 10.9.0.110(45201) [4079203] 67122b3b.3e3e63 2024-10-18 12:32:44.261 EEST SMA amantzio@dynacom line:36 LOG: duration: 0.553 ms bind /C_5: SELECT work_status FROM company_stuff WHERE ldap_cn = $1 10.9.0.110(45201) [4079203] 67122b3b.3e3e63 2024-10-18 12:32:44.261 EEST SMA amantzio@dynacom line:38 LOG: duration: 0.036 ms execute /C_5: SELECT work_status FROM company_stuff WHERE ldap_ cn = $1 So the parse is done on an unnamed prepared statement, however the bind and the execute show this : /C_5 after. We haven't got any log entries with this /C_* pattern on the "parse" phase, only on "bind" and "execute". I am curious what those represent. Thank you --------------G0u98XYsz0tRoo0S0RdZsn6b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

Hi All

We have disabled prepared statements in the JDBC settings (prepareThreshold=0) and in pgbouncer (max_prepared_statements=0).

I have noticed in the pgsql 16.4 logs some lines with this pattern :

10.9.0.110(45201) [4079203] 67122b3b.3e3e63 2024-10-18 12:32:44.260 EEST SMA amantzio@dynacom line:35 LOG: duration: 0.166 ms parse <unnamed>: SELECT work_status FROM company_stuff WHERE ldap_cn = $
1
10.9.0.110(45201) [4079203] 67122b3b.3e3e63 2024-10-18 12:32:44.261 EEST SMA amantzio@dynacom line:36 LOG: duration: 0.553 ms bind <unnamed>/C_5: SELECT work_status FROM company_stuff WHERE ldap_cn
= $1
10.9.0.110(45201) [4079203] 67122b3b.3e3e63 2024-10-18 12:32:44.261 EEST SMA amantzio@dynacom line:38 LOG: duration: 0.036 ms execute <unnamed>/C_5: SELECT work_status FROM company_stuff WHERE ldap_
cn = $1

So the parse is done on an unnamed prepared statement, however the bind and the execute show this : /C_5 after <unnamed>. We haven't got any log entries with this /C_* pattern on the "parse" phase, only on "bind" and "execute". I am curious what those represent.

Thank you

--------------G0u98XYsz0tRoo0S0RdZsn6b--