Re: point_ops for GiST - Mailing list pgsql-hackers

From Robert Haas
Subject Re: point_ops for GiST
Date
Msg-id 603c8f070912310853g1d27d2c9hdb753bc116111961@mail.gmail.com
Whole thread Raw
In response to Re: point_ops for GiST  (Teodor Sigaev <teodor@sigaev.ru>)
Responses Re: point_ops for GiST  (Teodor Sigaev <teodor@sigaev.ru>)
Re: point_ops for GiST  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
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.

Beyond that, I have a variety of minor whitespace and commenting
suggestions, so I am attaching an updated version of the patch as well
as an incremental diff between your version and mine, for your
consideration.  The changes are: (1) comment reuse of gist_box
functions for point_ops, (2) format point ops function analogously to
existing sections in same file, (3) uncuddle opening braces, (4)
adjust indentation and spacing in a few places, (5) rename
StrategyNumberOffsetRange to GeoStrategyNumberOffset, and (6) use a
plain block instead of do {} while (0) - the latter construct is
really only needed in certain types of macros.

...Robert

Attachment

pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: uintptr_t for Datum
Next
From: Tom Lane
Date:
Subject: Re: Re-enabling SET ROLE in security definer functions