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

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Jeff Davis <pgsql(at)j-davis(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: GiST for range types (was Re: Range Types - typo + NULL string constructor)
Date: 2011-10-25 18:48:05
Message-ID: CAPpHfdvBZEoDjdYKdV5nbB_P7Q5DUSRZS3HmZS4xb-Fc=7qieQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 24, 2011 at 3:05 PM, Alexander Korotkov <aekorotkov(at)gmail(dot)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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Euler Taveira de Oliveira 2011-10-25 19:56:12 autovacuum workers warning
Previous Message Sushant Sinha 2011-10-25 18:15:17 Re: lexemes in prefix search going through dictionary modifications