On Fri, Feb 24, 2012 at 10:46 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > I believe it's still somewhat common among JDBC users to force > V2-protocol connections as a workaround for over-eager prepared > statement planning. Although I think the issue they're trying to dodge > will be fixed as of 9.2, that doesn't mean the server-side support can > go away.
good point. I just went through this. The JDBC driver has a 'prepareThreshold' directive that *mostly* disables server side prepared statements so you can work with tools like pgbouncer. Unfortunately, it doesn't work for explicit transaction control statements so that you have to downgrade jdbc protocol or patch the driver (which is really the better way to go, but I can understand why that won't fly for a lot of people). merlin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
