> On Sep 12, 2017, at 1:07 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > > [ changing subject line to possibly draw more attention ] > > Mark Dilger <hornschnor...@gmail.com> writes: >>> On Apr 5, 2017, at 9:23 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: >>> In short, if you are supposed to write >>> FOO *val = PG_GETARG_FOO(n); >>> then the macro designer blew it, because the name implies that it >>> returns FOO, not pointer to FOO. This should be >>> FOO *val = PG_GETARG_FOO_P(n); > >> I have written a patch to fix these macro definitions across src/ and >> contrib/. >
Thanks, Tom, for reviewing my patch. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
