Migrating from 10 -> 16, PreparedStatements disabled in JDBC and pgbouncer, I am getting : bind <unnamed>/C_5

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(at)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(at)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(at)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