Opened 12 years ago
Closed 6 years ago
#1447 closed enhancement (invalid)
geometry op class for index only scans (PostgreSQL 9.2+)
| Reported by: | robe | Owned by: | pramsey |
|---|---|---|---|
| Priority: | medium | Milestone: | PostGIS Fund Me |
| Component: | postgis | Version: | master |
| Keywords: | Cc: |
Description
PostgreSQL 9.2 now supports index only scans. Originally I thought we couldn't take advantage of it, but I suspect it might help with quick && count checks.
See this thread.
http://archives.postgresql.org/pgsql-hackers/2012-01/msg00414.php sadly this won't help much with the more useful use case of
ST_Intersects(… ) as that still needs to pull the geometry though I guess it would only need in the case of if index check passes so might still be very useful. Dunno.
Change History (3)
comment:1 by , 11 years ago
| Milestone: | PostGIS 2.1.0 → PostGIS Future |
|---|
comment:2 by , 7 years ago
| Milestone: | PostGIS Future → PostGIS Fund Me |
|---|
comment:3 by , 6 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
I don't believe index-only scans are going to be useful for us ever, since we don't have the object in the index.
Note:
See TracTickets
for help on using tickets.
Milestone renamed