On Wed, Mar 29, 2017 at 11:54 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Andres Freund <and...@anarazel.de> writes: >> we have a good number of '(GISTENTRY *) PG_GETARG_POINTER(n)' in our >> code - looks a bit better & shorter to have PG_GETARG_GISTENTRY(n). > > Should be PG_GETARG_GISTENTRY_P to match existing conventions, > otherwise +1
I have never quite understood why some of those macros have _P or _PP on the end and others don't. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
