Re: SP-GiST for ranges based on 2d-mapping and quad-tree - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: SP-GiST for ranges based on 2d-mapping and quad-tree
Date
Msg-id CAPpHfdtVYrKFD3hj=fBqWR6mRhCouCPJDgOiu_63A7U_4KzNSA@mail.gmail.com
Whole thread Raw
In response to Re: SP-GiST for ranges based on 2d-mapping and quad-tree  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: SP-GiST for ranges based on 2d-mapping and quad-tree  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Re: SP-GiST for ranges based on 2d-mapping and quad-tree  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
On Thu, Jul 12, 2012 at 10:29 AM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote:
On 12.07.2012 02:11, Alexander Korotkov wrote:
On Thu, Jul 12, 2012 at 3:03 AM, Alexander Korotkov<aekorotkov@gmail.com>wrote:

On Tue, Jul 3, 2012 at 10:51 AM, Jeff Davis<pgsql@j-davis.com>  wrote:

Also, it would be helpful to add a couple tests to rangetypes.sql.


New version of patch is attached.


Oops, forgot to include one comment fix into patch.

Thanks. Can you do something about TrickFunctionCall2, please? (http://archives.postgresql.org/message-id/4FE2C968.2010503@enterprisedb.com) A separate patch to refactor that in the existing gist opclass would probably be best.

Done. There are separate patch for get rid of TrickFunctionCall2 and version of SP-GiST for ranges based on that patch.

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

pgsql-hackers by date:

Previous
From: Gurjeet Singh
Date:
Subject: Re: FW: Allow replacement of bloated primary key indexes without foreign key rebuilds
Next
From: Gurjeet Singh
Date:
Subject: Re: Re: Allow replacement of bloated primary key indexes without foreign key rebuilds