network profile
| bio | website | michaelkeutel.de |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 5 months |
| seen | Dec 20 '12 at 20:02 | |
| stats | profile views | 2 |
|
Dec 20 |
awarded | Supporter |
|
Dec 20 |
awarded | Scholar |
|
Dec 20 |
accepted | Postgres/Postgis spatial index - no speed up |
|
Dec 20 |
comment |
Postgres/Postgis spatial index - no speed up Yes I see, I need this query to involve the index boundary test. Thx Alexandre. (I'll mark unicoletti as solution, as he was fast and cleared the issue to me) |
|
Dec 20 |
comment |
Postgres/Postgis spatial index - no speed up That makes the issue more clear to me. I will try it. So if I put the ST_Contains() query into the WHERE clause, the spatial index should actually be helpful? I think I have to reorganize my script to call ST_Contains within WHERE clause. At the moment I am iterating through all polygons and always test two of them seperately. |
|
Dec 20 |
awarded | Student |
|
Dec 20 |
asked | Postgres/Postgis spatial index - no speed up |
