Re: GiST for range types (was Re: Range Types - typo + NULL string constructor) - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: GiST for range types (was Re: Range Types - typo + NULL string constructor)
Date
Msg-id CAPpHfdvBZEoDjdYKdV5nbB_P7Q5DUSRZS3HmZS4xb-Fc=7qieQ@mail.gmail.com
Whole thread Raw
In response to Re: GiST for range types (was Re: Range Types - typo + NULL string constructor)  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-hackers
On Mon, Oct 24, 2011 at 3:05 PM, Alexander Korotkov <aekorotkov@gmail.com> wrote:
If we allow user to specify own gist_penalty function, then such function should deal with:
1) GiST-specific data structures such as GISTENTRY.
2) Decomposing ranges using range_deserialize.
3) Inifinities, which we could handle in general penalty functions.
Thats why I prefere to implement subtype_diff.
I forgot another agument for having subtype_diff:
4) In my picksplit algorithm it would be more natural to use subtype_diff for measuring overlap than use penalty function.

------
With best regards,
Alexander Korotkov. 

pgsql-hackers by date:

Previous
From: Sushant Sinha
Date:
Subject: Re: lexemes in prefix search going through dictionary modifications
Next
From: "Erik Rijkers"
Date:
Subject: Re: (PATCH) Adding CORRESPONDING to Set Operations