Migrating from 10 -> 16, PreparedStatements disabled in JDBC and pgbouncer, I am getting : bind /C_5 - Mailing list pgsql-admin

From Achilleas Mantzios - cloud
Subject Migrating from 10 -> 16, PreparedStatements disabled in JDBC and pgbouncer, I am getting : bind /C_5
Date
Msg-id b661cc9f-da73-4c41-aba8-0bd680a6085c@cloud.gatewaynet.com
Whole thread Raw
Responses Re: Migrating from 10 -> 16, PreparedStatements disabled in JDBC and pgbouncer, I am getting : bind /C_5
List pgsql-admin

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

pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: [EXT] Re: 101 Grants and Access Right Table/View
Next
From: Tom Lane
Date:
Subject: Re: Migrating from 10 -> 16, PreparedStatements disabled in JDBC and pgbouncer, I am getting : bind /C_5