Re: point_ops for GiST
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Teodor Sigaev <teodor@sigaev.ru>
Cc: Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2010-01-11T18:17:25Z
Lists: pgsql-hackers
2010/1/11 Teodor Sigaev <teodor@sigaev.ru>: >> I have reviewed this patch and it looks good to me. The only >> substantive question I have is why gist_point_consistent() uses a >> different coding pattern for the box case than it does for the polygon >> and circle cases? It's not obvious to me on the face of it why these >> aren't consistent. > > gist_circle_consistent/gist_poly_consistent set recheck flag to true because > corresponding index contains only bounding box of indexed values > (circle/polygon). gist_point_consistent could do an exact check. Will add a > coments. Make sense. A comment sounds good. >> Beyond that, I have a variety of minor whitespace and commenting >> suggestions, so I am attaching an updated version of the patch as well > > Agree with your changes. Suppose, there is no objection to commit it? No, I think it looks good... if no one else chimes in with objections in the next day or two I would go ahead. ...Robert
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Fix gist_box_same and gist_point_consistent to handle fuzziness correctly.
- 3c29b196b0ce 9.3.0 cited
-
Add point_ops opclass for GiST.
- 4cbe47393877 9.0.0 cited