| From: | Vinicius Abrahao <vinnix(dot)bsd(at)gmail(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Maciek Sakrejda <m(dot)sakrejda(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-25 19:17:38 |
| Message-ID: | CAM9BftyxfNN0ouWo7hQ5yFK=hN1xBGs+ri95R4BWk9wboU3vYA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, Jul 25, 2012 at 3:45 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> 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.
>
indeed!
Is there any reason for that?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2012-07-25 19:26:15 | Re: Geoserver-PostGIS performance problems |
| Previous Message | Merlin Moncure | 2012-07-25 18:45:44 | Re: Geoserver-PostGIS performance problems |