Re: debugging: prepared statement "dbdpg_7" already exists

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


> Prepared statements break immediately using pgpool.

Yes, I've been digging into this a little bit, and while I
don't like what pgpool is doing (namely, living under the
assumption that one database session will be exactly equivalent
to the rest), I think we can work around this in DBD::Pg.
Ideally, the statement handle would go out of scope before
disconnecting and all the prepared statements would be deallocated,
but I'll probably add a switch to connect which will prevent
the overlap of prepared statement names you are currently seeing.

- --
Greg Sabino Mullane greg-738XdyZ4GzZWk0Htik3J/[email protected]
PGP Key: 0x14964AC8 200605082034
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFEX+k1vJuQZxSWSsgRArH3AKD8iQyUY64wZkX0BT/u2Zk8KCpGgACfYT65
+YLprjco7fCavJxSqdv17sM=
=grPZ
-----END PGP SIGNATURE-----