Horton
Menu

Re: Geoserver-PostGIS performance problems

Merlin Moncure <mmoncure@gmail.com>

View thread
From: Merlin Moncure <mmoncure@gmail.com>
To: Maciek Sakrejda <m.sakrejda@gmail.com>
Cc: Vinicius Abrahao <vinnix.bsd@gmail.com>, Riaan van den Dool <rvddool@csir.co.za>, Brett Walker <brett.walker@geometryit.com>, "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Date: 2012-07-26T13:32:21Z
Lists: pgsql-performance 
On Thu, Jul 26, 2012 at 1:34 AM, Maciek Sakrejda <m.sakrejda@gmail.com> wrote:
>> unfortunately postgres jdbc is bugged and does not honor the above for
>> transaction control commands (begin, commit, etc).  This patch
>> http://treehou.se/~omar/postgresql-jdbc-8.4-701-pgbouncer_txn.patch
>> will fix it, assuming it hasn't been fixed in recent postgres jdbc.
>
> Looks like it's still an issue:
> https://github.com/pgjdbc/pgjdbc/blob/master/org/postgresql/core/v3/QueryExecutorImpl.java#L426
>
> Although I don't quite follow why it's an issue in the first
> place--isn't the point to avoid creating a plan with parameter markers
> but not actual parameter information? BEGIN, COMMIT, et al never have
> markers in the first place. What am I missing?

This causes problems for connection poolers.  (see;
http://pgbouncer.projects.postgresql.org/doc/faq.html#_disabling_prepared_statements_in_jdbc).

merlin