Order problem in GiST index - Mailing list pgsql-hackers

From Kotroczó Roland
Subject Order problem in GiST index
Date
Msg-id DB4PR10MB69669979A286F619D74ECB62B16E9@DB4PR10MB6966.EURPRD10.PROD.OUTLOOK.COM
Whole thread Raw
List pgsql-hackers

Hi! 

We are developing a GiST index structure. We use M-tree for this work. We have a problem with it. We would like to get some closest neighbors. In my select we order the query by distance, and we use limit. Sometimes it works well, but in some cases I don’t get back the closest points. If we set the recheck flag to true, the query results will be correct. 

I examined the CUBE extension and realized the recheck flag is false. According to the comments, it’s not necessary to set the recheck to true in CUBE. What conditions must be met to work well even with recheck=false? How is it working in CUBE? 

Thanks for your replies. 

pgsql-hackers by date:

Previous
From: Eric Ridge
Date:
Subject: Re: [PATCH] Support % wildcard in extension upgrade filenames
Next
From: "Regina Obe"
Date:
Subject: RE: [PATCH] Support % wildcard in extension upgrade filenames