| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> |
| Cc: | 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-25 18:45:44 |
| Message-ID: | CAHyXU0wS9V_k70gEMA7qGCL3nOvZE58TSTuz0W6hXSFEgBdD6w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Jul 24, 2012 at 10:50 AM, Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com> wrote:
> This may be another issue of the problem discussed here:
> http://postgresql.1045698.n5.nabble.com/avoid-prepared-statements-on-complex-queries-td4996363.html
> (Kris Jurka explains the crux of it in that thread).
>
> Note that it seems the preparing/planning interaction was not the
> poster's actual problem, but it may have been yours. As Tom Lane notes
> in that thread, this should get better in 9.2.
jdbc should get some blame too -- it's really aggressive about
preparing queries.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vinicius Abrahao | 2012-07-25 19:17:38 | Re: Geoserver-PostGIS performance problems |
| Previous Message | Marcus Engene | 2012-07-25 18:11:55 | Re: odd planner again, pg 9.0.8 |