csmith writes:
> ... It's as if the
> query is considering tuples in "catalog" outside of the view's domain.
This isn't particularly surprising: the planner will feel free to push
that WHERE condition down as far as it can. Probably there is some
aspect of the view definition that prevented suc
This should be addressed to the Postgis list.
However, you are spatially joining two geometries, and they need be in the same
coordinate system.
The column "the_geom" has a defined SRID (spatial reference id) when created in
it's original table. Your hard coded POLYGON in the SQL below has a SR
Hello,
I serve a Geospatial IS project that for some years has used PostgreSQL
and PostGIS. A strategy/scheme that has worked for all previous
versions has failed with a recent upgrade to 8.3 (e.g. 8.3.6-1).
Relation "catalog" is a large geospatially-enabled aggregation of data
with a varie
