Re: max(*) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: max(*)
Date
Msg-id 28527.1148672271@sss.pgh.pa.us
Whole thread Raw
In response to Re: max(*)  ("Jim C. Nasby" <jnasby@pervasive.com>)
List pgsql-hackers
"Jim C. Nasby" <jnasby@pervasive.com> writes:
> My concern is that it's not inconceiveable to typo max(field) into
> max(*), which could make for a rather frustrating error. Not to mention
> this being something that could trip newbies up. If nothing else I'd say
> it warrants a %TODO just so it doesn't end up on the PostgreSQL gotcha's
> page. :)

count(*) has been implemented that way since about 1999, and no one's
complained yet, so I think you are overstating the importance of the
problem.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruno Wolff III
Date:
Subject: Re: max(*)
Next
From: Andreas Seltenreich
Date:
Subject: Re: GIN stuck in loop during PITR