| From: | Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Vinicius Abrahao <vinnix(dot)bsd(at)gmail(dot)com>, Riaan van den Dool <rvddool(at)csir(dot)co(dot)za>, Brett Walker <brett(dot)walker(at)geometryit(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Geoserver-PostGIS performance problems |
| Date: | 2012-07-26 06:34:17 |
| Message-ID: | CAOtHd0A0cr2-H1e8Rex_1gKBXOF6i0_dUyX_GJXmdHYOyS7dTA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> 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?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Maciek Sakrejda | 2012-07-26 06:51:33 | Re: Geoserver-PostGIS performance problems |
| Previous Message | Rural Hunter | 2012-07-26 02:13:48 | Re: Geoserver-PostGIS performance problems |