-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160
> We are using pgbouncer and seeing these errors in the postgresql logs.
> ...ERROR: prepared statement "dbdpg_p1573_3968" does not exist
>
> I don't believe pgbouncer allows for server prepared statements,
> so why would I see anything in the logs at all?
Because you are using prepared statements. :) You are probably running pgbouncer
at the "transaction" level, in which case you need to do this inside DBD::Pg
right after the initial connection:
$dbh->{pg_server_prepare} = 0;
This will prevent DBD::Pg from using server-side prepares. There's a small cost
to this, but it's usually overshadowed by the efficiency savings of using
pgbouncer.
- --
Greg Sabino Mullane g...@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200911051621
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iEYEAREDAAYFAkrzQh4ACgkQvJuQZxSWSsg3rACfVejcM3ZJg4yF1ehLB9YbDoMZ
6uUAn0MDvjHqH5ackLznQxTjVBMJUZHm
=Odco
-----END PGP SIGNATURE-----
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
