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-07 08:21:41 |
Message-ID: | 82bp3ti0oa.fsf@mid.bfk.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Jeff Davis:
> On Tue, 2011-01-04 at 14:18 +0000, Florian Weimer wrote:
>> * 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?
> Can you clarify what you mean? I don't know what the "eqsel hint" is.
Uhm, it's not not eqsel, but the RESTRICT clause on operators:
<http://www.postgresql.org/docs/8.4/static/xoper-optimization.html>
I'm wondering if one of these hint functions can be reused to compute
range lengths.
--
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 | Dimitri Fontaine | 2011-01-07 08:24:23 | Re: making an unlogged table logged |
Previous Message | Itagaki Takahiro | 2011-01-07 07:34:33 | Re: [TEST REPORT] 9.1Alpha3 Feature E.1.4.7.2 in release notes. |