Skip site navigation (1) Skip section navigation (2)

Re: Geoserver-PostGIS performance problems

From: Maciek Sakrejda <m(dot)sakrejda(at)gmail(dot)com>
To: Riaan van den Dool <rvddool(at)csir(dot)co(dot)za>
Cc: 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-24 15:50:42
Message-ID: CAOtHd0Ai_SMfU7G2k9j+bXqrKJYMQQchoRqU_qiFGyvmv7m8QA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
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.

In response to

Responses

pgsql-performance by date

Next:From: Tom LaneDate: 2012-07-24 15:55:25
Subject: Re: Using ctid column changes plan drastically
Previous:From: Thomas KellererDate: 2012-07-24 14:54:18
Subject: Re: Using ctid column changes plan drastically

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group