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

From Tom Lane
Subject Re: Incorrect behaviour when using a GiST index on points
Date
Msg-id 7948.1341329664@sss.pgh.pa.us
Whole thread Raw
In response to Re: Incorrect behaviour when using a GiST index on points  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Incorrect behaviour when using a GiST index on points  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Thu, Jun 21, 2012 at 2:53 PM, Alexander Korotkov
> <aekorotkov@gmail.com> wrote:
>> 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?

> Do we need to apply this patch to 9.2?

It's been like that all along, no?  I'm feeling hesitant to shove it
into 9.2 at this late date.  But we should review it and get it into
9.3 early if possible.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [Review] Add SPI_gettypmod() to return a field's typemod from a TupleDesc
Next
From: Robert Haas
Date:
Subject: Re: [Review] Prevent the specification of conflicting transaction read/write options