Re: Lots of incorrect comments in nodeFuncs.c - Mailing list pgsql-hackers

From David Rowley
Subject Re: Lots of incorrect comments in nodeFuncs.c
Date
Msg-id CAApHDvoCkOQze=f__TQ2uq2SOdWRqx-TNf9m2PQERPdppmWxNA@mail.gmail.com
Whole thread Raw
In response to Re: Lots of incorrect comments in nodeFuncs.c  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Lots of incorrect comments in nodeFuncs.c
List pgsql-hackers
On Fri, 9 Apr 2021 at 10:11, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> David Rowley <dgrowleyml@gmail.com> writes:
> > I noticed that nodeFuncs.c appears to have some pretty sloppy work
> > done in many of the comments.  Many look like they've just not been
> > updated from a copy/paste/edit from another node function.
> > The attached aims to clean these up.
>
> I believe every one of these changes is wrong.
> For instance:
>
>                 case T_ScalarArrayOpExpr:
> -                       coll = InvalidOid;      /* result is always boolean */
> +                       coll = InvalidOid;      /* result is always InvalidOid */
>                         break;
>
> The point here is that the result type of ScalarArrayOpExpr is boolean,
> which has no collation, therefore reporting its collation as InvalidOid
> is correct.  Maybe there's a clearer way to say that, but your text is
> more confusing not less so.

hmm ok.  I imagine there must be a better way to say that then since
it confused at least 1 reader so far.  My problem is that I assumed
"result" meant the result of the function that the comment is written
in, not the result of evaluating the given expression during
execution. If that was more clear then I'd not have been misled.

David



pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Binary search in ScalarArrayOpExpr for OR'd constant arrays
Next
From: Michael Paquier
Date:
Subject: Re: test runner (was Re: SQL-standard function body)