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

From Noah Misch
Subject Re: Incorrect behaviour when using a GiST index on points
Date
Msg-id 20121011111728.GE29677@tornado.leadboat.com
Whole thread Raw
In response to Re: Incorrect behaviour when using a GiST index on points  (Noah Misch <noah@leadboat.com>)
Responses Re: Incorrect behaviour when using a GiST index on points  (Noah Misch <noah@leadboat.com>)
List pgsql-hackers
On Tue, Oct 02, 2012 at 01:58:40PM -0400, Noah Misch wrote:
> > > On Mon, Aug 27, 2012 at 7:43 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > >> There's also the big-picture question of whether we should just get rid
> > >> of fuzzy comparisons in the geometric types instead of trying to hack
> > >> indexes to work around them.

> In any event, I think we should entertain a patch to make the GiST operator
> class methods bug-compatible with corresponding operators.  Even if we decide
> to change operator behavior in HEAD, the back branches could use it.

We have broad agreement that the specific implementation of fuzz in geometric
comparison operators is shoddy, but nobody has voiced interest in designing a
concrete improvement.  I propose adding a TODO item "Remove or improve
rounding in geometric comparison operators", endorsing Alexander's design, and
reviewing his patch.  Objections?



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: tuplesort memory usage: grow_memtuples
Next
From: Noah Misch
Date:
Subject: Re: September 2012 commitfest