On 5/8/2014 7:07 AM, Paul Ramsey wrote:
Roxanne, you seem to have isolated the problem to a particular
geometry column, which speaks to this being a PostGIS problem.
ok - wrong list - sorry!
Since the analyze code was re-written in 2.1, and your issue is coming
up in a 2.0>2.1 upgrade, that further points to the issue potentially
being a PostGIS problem. Unless the same data works in a PgSQL
9.2/PostGIS 2.1 combo, it seems clear that PgSQL 9.3 is not the
culprit here. (Though I would love to be reassured that 9.2/2.1 combo
also does not work, since that eliminates a bad interaction between
9.3/2.1 as the issue.)
At some point in order to debug I’ll probably need a copy of the data,
or access to a system that has the data and a dev environment. Please
do file a ticket at http://trac.osgeo.org/postgis on this issue.
Thanks Paul,
I will see if we can trim the specific scenario down a little more for
you and then file (data volume at least).
Roxanne
