Re: point_ops for GiST
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Teodor Sigaev <teodor@sigaev.ru>,
Pgsql Hackers <pgsql-hackers@postgresql.org>
Date: 2015-05-12T18:13:33Z
Lists: pgsql-hackers
Alvaro Herrera wrote: > Robert Haas wrote: > > 2009/12/30 Teodor Sigaev <teodor@sigaev.ru>: > > > Sync with current CVS > > > > 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. > > Emre Hasegeli just pointed out to me that this patch introduced > box_contain_pt() and in doing so used straight C comparison (<= etc) > instead of FPlt() and friends. (This is commit 4cbe473938779ec414d90c2063c4398e68a70838) -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
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