Skip site navigation (1) Skip section navigation (2)

Re: Incorrect behaviour when using a GiST index on points

From: Oleg Bartunov <obartunov(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alexander Korotkov <aekorotkov(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(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
Date: 2012-07-03 15:48:41
Message-ID: CAF4Au4yhNu_HCFAP=57ur_frdTUMD3tKH_gF3T79RXBpDJgEVA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Yes, it's a bug and it needs to be applied !

On Tue, Jul 3, 2012 at 7:44 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Jul 3, 2012 at 11:34 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> On Thu, Jun 21, 2012 at 2:53 PM, Alexander Korotkov
>>> <aekorotkov(at)gmail(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2012-07-03 15:51:29
Subject: Re: Ability to listen on two unix sockets
Previous:From: Bruce MomjianDate: 2012-07-03 15:47:50
Subject: Re: Pruning the TODO list

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group