Timeline for PostGIS window function not picking up index?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 28, 2021 at 22:52 | history | edited | Erwin Brandstetter | CC BY-SA 4.0 |
update link
|
| Apr 27, 2017 at 2:33 | comment | added | Erwin Brandstetter |
@audlift-bit: Whether indexes are applicable is decided by operators, not functions (related: stackoverflow.com/a/29245753/939860). Some functions use operators under the hood, like many PostGis functions. The PostGIS manual mentions index support for each function. Example: ST_DWithin
|
|
| Apr 26, 2017 at 17:50 | comment | added | audlift-bit | @ErwinBrandstetter the PostGIS link discussing how to take advantage of index is especially interesting to me but quite dry! Would you by any chance know if there is something providing a list of indexable (spatial) PostGIS functions? | |
| Apr 20, 2017 at 13:38 | comment | added | Erwin Brandstetter | @audlift-bit: For a query like I display, it already pays to use the index with 4k rows while only one or very few rows are retrieved. And I added a link for deeper understanding above. | |
| Apr 20, 2017 at 13:38 | history | edited | Erwin Brandstetter | CC BY-SA 3.0 |
add links to manual
|
| Apr 20, 2017 at 11:11 | comment | added | audlift-bit | Thanks both. Indeed it is not picked up for only 3984 rows but for something of a little larger scale it is. Can you please elaborate a bit on some indications on whether a spatial index will be picked up? I know it has to do with costs but seems like there are some even more obvious indications before that. | |
| Apr 20, 2017 at 10:58 | vote | accept | audlift-bit | ||
| Apr 20, 2017 at 5:37 | comment | added | user1822 | Plus: for only 3984 rows, The index wouldn't probably used either. | |
| Apr 20, 2017 at 2:07 | history | answered | Erwin Brandstetter | CC BY-SA 3.0 |