Horton

Re: Incorrect behaviour when using a GiST index on points

Robert Haas <robertmhaas@gmail.com>

View thread
From: Robert Haas <robertmhaas@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alexander Korotkov <aekorotkov@gmail.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Oleg Bartunov <obartunov@gmail.com>, Teodor Sigaev <teodor@sigaev.ru>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2012-07-03T15:44:13Z
Lists: pgsql-hackers 
On Tue, Jul 3, 2012 at 11:34 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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?

Yeah, but it seems an awful lot like a bug.  In fact... it's hard to
imagine how it could be any more of a bug than this.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company