Il 20/08/11 04:28, Tom Lane ha scritto:
Edoardo Panfili<edoa...@aspix.it> writes:
[ poor plan for a Postgis query with ]
Postgres 8.4.8 with postgis 1.5.3
I think that most of the issue here is poor selectivity estimation for
the Postgis operations, particularly&&. I suggest that you should ask
about this on the postgis mailing lists. They might well tell you to
try a newer release --- they may have improved things since 1.5.3.
1.5.3 is the latest stable release, I am downloading 2.0.0SVN
NOTICE: LWGEOM_gist_joinsel called with incorrect join type
You should *definitely* report that to the Postgis guys, because it's a
bug.
I will do it
Thank you
Edoardo Panfili
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
