You need to use proper datatypes in @postgis; My Query went from 2200ms to 0.5 ms when my data went from Geometry to Geography
@devten85 No, not the cast. Having a native geography index is what made the difference.
-
-
@postgis Maybe I'm not getting this, but is there a way to keep data in geometry and have a geography index? -
@devten85 Yes, if you use a functional index, like CREATE INDEX x ON t USING GIST (geography(geom)); - 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.