Re: Double sorting split patch - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Double sorting split patch
Date
Msg-id CAPpHfdtJL16zZ2uwD5LD8TnkchV-TFaLbYJeGk0ZkhcFb=KeDA@mail.gmail.com
Whole thread Raw
In response to Re: Double sorting split patch  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: Double sorting split patch  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Thu, Oct 6, 2011 at 11:06 AM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:
On 05.10.2011 15:59, Alexander Korotkov wrote:
Path without allocating extra bytes is attached.
I run some more detailed tests on geonames and two smaller datasets from
rtreeportal.org.

Ok, thanks. Looks good to me now, so committed.
Thanks. I'm going to continue work on application of this split method in following areas:
1) range types
2) seg contrib module
3) cube contrib module (there situation is not so easy, probably some heuristic of split method selection would be required)
Do you think that separation of some common parts of algorithm implemetation is resonable in order to avoid code duplication? For example, different application of algorithm could share function of splits enumeration along axis which takes pointer to consider_split as an argument.

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

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Double sorting split patch
Next
From: Nikhil Sontakke
Date:
Subject: Re: Review: Non-inheritable check constraints