public inbox for [email protected]
help / color / mirror / Atom feedPgBouncer Prepared Statement ERROR
3+ messages / 3 participants
[nested] [flat]
* PgBouncer Prepared Statement ERROR
@ 2025-07-18 12:52 KK CHN <[email protected]>
2025-07-18 13:32 ` Re: PgBouncer Prepared Statement ERROR Greg Sabino Mullane <[email protected]>
2025-07-18 13:34 ` Re: PgBouncer Prepared Statement ERROR Laurenz Albe <[email protected]>
0 siblings, 2 replies; 3+ messages in thread
From: KK CHN @ 2025-07-18 12:52 UTC (permalink / raw)
To: [email protected]
Hi ,
I am getting error when using PgBouncer(1.23.1 ) with Postgres 16
(RedHAT 9.4)
2025-07-18 00:00:00 IST ERROR: prepared statement "S_243" does not exist
2025-07-18 00:00:03 IST ERROR: prepared statement "S_205" does not exist
2025-07-18 00:00:03 IST ERROR: prepared statement "S_206" does not exist
2025-07-18 00:00:03 IST ERROR: prepared statement "S_207" does not exist
How to avoid these prepared statement Errors ?
Any hints most welcome,
Krishane
config as follows
[root@pgbouncer ~]# grep ^[^';;;'] /usr/local/etc/pgbouncer.ini
[databases]
transaction_db = host=dbmain.erss.in port=5444 dbname= transaction_db
mgt_db = host=dbmain.erss.in port=5444 dbname=mgt_db
....................................
tsp_db = host=dbmain.erss.in port=5444 dbname=tsp_db
[users]
[pgbouncer]
logfile = /var/log/pgbouncer/pgbouncer.log
pidfile = /var/run/pgbouncer/pgbouncer.pid
listen_addr = *
listen_port = 5444
auth_type = md5
auth_file = /usr/local/etc/pgbouncer.users
admin_users = myuser
stats_users = status_user,
pool_mode = transaction
server_reset_query = DISCARD ALL
server_reset_query_always = 1
ignore_startup_parameters = extra_float_digits, options, statement_timeout,
idle_in_transaction_session_timeout
max_client_conn = 5000
default_pool_size = 20
min_pool_size = 10
reserve_pool_size = 10
reserve_pool_timeout = 5
max_db_connections = 900
max_user_connections = 800
server_lifetime = 3600
server_idle_timeout = 60000
[root@pgbouncer ~]#
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: PgBouncer Prepared Statement ERROR
2025-07-18 12:52 PgBouncer Prepared Statement ERROR KK CHN <[email protected]>
@ 2025-07-18 13:32 ` Greg Sabino Mullane <[email protected]>
1 sibling, 0 replies; 3+ messages in thread
From: Greg Sabino Mullane @ 2025-07-18 13:32 UTC (permalink / raw)
To: KK CHN <[email protected]>; +Cc: [email protected]
Make sure max_prepared_statements is set to nonzero in your config. See:
https://www.crunchydata.com/blog/prepared-statements-in-transaction-mode-for-pgbouncer
Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: PgBouncer Prepared Statement ERROR
2025-07-18 12:52 PgBouncer Prepared Statement ERROR KK CHN <[email protected]>
@ 2025-07-18 13:34 ` Laurenz Albe <[email protected]>
1 sibling, 0 replies; 3+ messages in thread
From: Laurenz Albe @ 2025-07-18 13:34 UTC (permalink / raw)
To: KK CHN <[email protected]>; [email protected]
On Fri, 2025-07-18 at 18:22 +0530, KK CHN wrote:
> I am getting error when using PgBouncer(1.23.1 ) with Postgres 16 (RedHAT 9.4)
>
> 2025-07-18 00:00:00 IST ERROR: prepared statement "S_243" does not exist
> 2025-07-18 00:00:03 IST ERROR: prepared statement "S_205" does not exist
> 2025-07-18 00:00:03 IST ERROR: prepared statement "S_206" does not exist
> 2025-07-18 00:00:03 IST ERROR: prepared statement "S_207" does not exist
>
> How to avoid these prepared statement Errors ?
Use a recent version of pgBouncer and set "max_prepared_statements"
high enough.
Yours,
Laurenz Albe
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2025-07-18 13:34 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-07-18 12:52 PgBouncer Prepared Statement ERROR KK CHN <[email protected]>
2025-07-18 13:32 ` Greg Sabino Mullane <[email protected]>
2025-07-18 13:34 ` Laurenz Albe <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox