Re: Incorrect behaviour when using a GiST index on points - Mailing list pgsql-hackers

From Alexander Korotkov
Subject Re: Incorrect behaviour when using a GiST index on points
Date
Msg-id CAPpHfdvbkS6DAbM9uOJLUY6dNVZpunLTF8G1Yoj5ruKiVMPXcg@mail.gmail.com
Whole thread Raw
In response to Re: Incorrect behaviour when using a GiST index on points  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: Incorrect behaviour when using a GiST index on points  (Robert Haas <robertmhaas@gmail.com>)
Re: Incorrect behaviour when using a GiST index on points  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Wed, Feb 22, 2012 at 5:56 PM, Alexander Korotkov <aekorotkov@gmail.com> wrote:
Attached patch fixes GiST behaviour without altering operators behaviour. 

I think we definitely should apply this patch before 9.2 release, because it is a bug fix. Otherwise people will continue produce incorrect GiST indexes with in-core geometrical opclasses until 9.3. Patch is very simple and only changes few lines of code.

Any thoughts?

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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Btree or not btree? That is the question
Next
From: Alvaro Herrera
Date:
Subject: Re: foreign key locks