| From: | Florian Weimer <fweimer(at)bfk(dot)de> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP: Range Types |
| Date: | 2011-01-04 14:18:18 |
| Message-ID: | 82fwt8pxat.fsf@mid.bfk.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Jeff Davis:
> 4. For the GiST penalty function, and perhaps some picksplit algorithms,
> it might be nice to know the length of a range, or do some other kinds
> of math. It introduces a lot of complexity to try to define math
> functions for each subtype, and try to make sure they behave sanely. So
> I was thinking that the user might need to specify a function that
> converts the subtype into a float that approximates a value's position
> in the total order.
Doesn't the eqsel hint already provide this information?
--
Florian Weimer <fweimer(at)bfk(dot)de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2011-01-04 14:23:40 | Re: texteq/byteaeq: avoid detoast |
| Previous Message | Pavel Stehule | 2011-01-04 14:13:11 | Re: texteq/byteaeq: avoid detoast |