| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: join selectivity |
| Date: | 2004-12-16 20:12:21 |
| Message-ID: | 87is72ngt6.fsf@stark.xeocode.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Mark Cave-Ayland" <m(dot)cave-ayland(at)webbased(dot)co(dot)uk> writes:
> Well at the moment PostGIS has a RESTRICT function that takes an expression
> of the form <column> <op> <constant> where column is a column consisting of
> geometries and constant is a bounding box. This is based upon histogram
> statistics and works well.
Are these functions that would be useful for GiST indexes in general?
What's involved in pulling them into a system? I mean, for example, a database
using RTREE (or GiST I guess) boxes and the @ operator.
I didn't realize anyone really had any idea where to start with gathering
statistics or writing selectivity functions for geometric types. It's great
news to hear there's actually work in this area.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Darcy Buskermolen | 2004-12-16 20:16:42 | port report: [FAILURE] FreeBSD 6, Intel icc7 |
| Previous Message | Adi Alurkar | 2004-12-16 20:06:46 | UNION ALL vs INHERITANCE |