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

From Tom Lane
Subject Re: Lots of incorrect comments in nodeFuncs.c
Date
Msg-id 1933940.1617919906@sss.pgh.pa.us
Whole thread Raw
In response to Lots of incorrect comments in nodeFuncs.c  (David Rowley <dgrowleyml@gmail.com>)
Responses Re: Lots of incorrect comments in nodeFuncs.c  (David Rowley <dgrowleyml@gmail.com>)
List pgsql-hackers
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.

Likewise, the point of the annotations in exprSetCollation is to not
let a collation be applied to a node that must have a noncollatable
result type.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pg_amcheck contrib application
Next
From: Mark Dilger
Date:
Subject: Re: pg_amcheck contrib application