From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stefan Keller <sfkeller(at)gmail(dot)com> |
Cc: | Jesper Krogh <jesper(at)krogh(dot)cc>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: SP-GiST versus index-only scans |
Date: | 2012-01-08 22:09:25 |
Message-ID: | 26843.1326060565@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Stefan Keller <sfkeller(at)gmail(dot)com> writes:
> There seems to exist some opportunities now with GIST which relate to
> geometry/geography types (but not only...):
> 1. Index-only scans on geometry columns with SP-GIST (being able to do
> a "SELECT id FROM my_table WHERE mygeom...;").
Well, if somebody builds an SP-GiST opclass for geometry, that should
work.
> 2. Index clustering incuding NULL values (i.e. being able to do a
> "CLUSTER mygeom_index ON mytable;" ).
Huh? GiST has supported nulls, and CLUSTER, since 8.2 or so. The
section of the PostGIS manual you're referring to seems to be years
out of date.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2012-01-08 22:17:10 | [PATCH] collation for (expr) |
Previous Message | Stefan Keller | 2012-01-08 21:53:45 | Re: SP-GiST versus index-only scans |