[postgis-users] ST_Overlaps and performance

[DrYSG]

However, a cold query to a completely new location using this syntax is
turning out to be much better.

SELECT * 
FROM portal.catalog as cat 
WHERE ST_Contains(cat.location,'SRID=4326;POINT(70.9433962
41.5384615)'::geometry) OR
      ST_Contains(cat.location,'SRID=4326;POINT(71.9433962
40.5384615)'::geometry)  ; 

 13:38:41  [SELECT - 27 row(s), 4.160 secs]  Result set fetched
... 1 statement(s) executed, 27 row(s) affected, exec/fetch time:
4.160/0.000 sec  [1 successful, 0 warnings, 0 errors]

I don't have to be fussy about the exact size of the QueryRectangle, it is
coming from a user drawing on a map.

However, the bbox's of the DB rectangles are aligned to lon/lat coordinates.



--
View this message in context: http://postgis.17.n6.nabble.com/ST-Overlaps-and-performance-tp4555465p4555690.html
Sent from the PostGIS - User mailing list archive at Nabble.com.