From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | David Fetter <david(at)fetter(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: WIP: RangeTypes |
Date: | 2011-01-29 19:00:42 |
Message-ID: | 9B3EF226-7C00-4216-8CEB-7CFEE68DBDAE@kineticode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Jan 29, 2011, at 10:57 AM, Jeff Davis wrote:
> On Fri, 2011-01-28 at 10:41 -0800, David E. Wheeler wrote:
>> +1 in principal. I think we should try to avoid the user of the term
>> "period" if possible, and I see definite benefits to a simple model of
>> $typename . 'range';
>
> Interesting, I didn't realize that PERIOD was such an undesirable type
> name.
It's not *hugely* undesirable. I just tend to think that "range" is more so.
>> Is there GIN support? GIN seems to be the preferred index type for
>> this sort of thing, no?
>
> GiST is the natural index access method if we approach ranges as a
> spatial type. I don't quite know what you have in mind for GIN; what
> keys would you extract from the value '[1.23,4.56)' ?
I think I'm just revealing my ignorance of these index types and what they're good for. My impression has been that GIN was a better but less-full-featured alternative to GiST and getting better with Tom's recent fixes for its handling of NULLs. But, uh, obviously not.
Best,
David
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2011-01-29 19:03:45 | Re: REVIEW: WIP: plpgsql - foreach in |
Previous Message | Jeff Davis | 2011-01-29 18:57:54 | Re: WIP: RangeTypes |