Thanks for the replies, interesting stuff.
I ended up using ST_ConvexHull(st_collect(geom)) in PostGIS (nice and fast) to
create a polygon covering all the points, and then I used FME to measure the
distance between all the vertices of that hull and the greatest distance was my
answer. The hull
I'm finally getting around to upgrading to Postgres 9.4 and I'm seeing long
query times on my Postgis database.
In Postgres 9.3.6, Postgis 2.1.7, I have a 70M record table of lines, with a
view that does a complex lookup to another 67M record non-geo table.
Extracting a small .2°x.2° area with
Hi William,
Did you run VACUUM ANALYZE on on the PG 9.4 table (after you imported
the data)? This would be required to have up-to-date statistics which
the query planner uses to e.g. decide if using an index would improve
query time.
And what is the query plan for your query (EXPLAIN ANALYZE)?
B
Yes, I vacuum analyzed.
I don't have an explain - I'm running this from ogr2ogr. I don't know how to
do the ogr2ogr -spat in sql.
On Jul 13, 2015, at 1:59 PM, Tom Kazimiers wrote:
> Hi William,
>
> Did you run VACUUM ANALYZE on on the PG 9.4 table (after you imported
> the data)? This would
You could turn logging on your database and see the query output in the log
file.
ALTER DATABASE mydb
SET log_statement = 'all';
Hope that helps,
Regina
-Original Message-
From: postgis-users-boun...@lists.osgeo.org
[mailto:postgis-users-boun...@lists.osgeo.org] On Behalf Of William
Ky
Jeez I'm an idiot.
I was confusing my view with a materialized view. After upgrading, when I saw
the materialized view I thought it was a leftover experiment that didn't work
(I recall having trouble setting that up) and trashed it. I only remember
using the dynamic view, but my memory can be
