Re: Incorrect behaviour when using a GiST index on points
From:
Robert Haas <robertmhaas(at)gmail(dot)com>
To:
Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc:
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Oleg Bartunov <obartunov(at)gmail(dot)com>, Teodor Sigaev <teodor(at)sigaev(dot)ru>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject:
Re: Incorrect behaviour when using a GiST index on points
On Thu, Jun 21, 2012 at 2:53 PM, Alexander Korotkov
<aekorotkov(at)gmail(dot)com> wrote:
> On Wed, Feb 22, 2012 at 5:56 PM, Alexander Korotkov <aekorotkov(at)gmail(dot)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?
Do we need to apply this patch to 9.2?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
