Re: Aggregate error message - Mailing list pgsql-hackers

From David Rowley
Subject Re: Aggregate error message
Date
Msg-id CAKJS1f8yYUYUfmjEZdDftsTNBqHaC=kEaiRGfQb9S0JoLxiN_w@mail.gmail.com
Whole thread Raw
In response to Aggregate error message  (Vik Fearing <vik.fearing@2ndquadrant.com>)
Responses Re: Aggregate error message  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, 24 May 2019 at 18:17, Vik Fearing <vik.fearing@2ndquadrant.com> wrote:
>
> With a sample query such as
>
> SELECT x, avg(x)
> FROM (VALUES (1), (2), (3)) AS v (x);
>
> We give the error message "column "v.x" must appear in the GROUP BY
> clause or be used in an aggregate function".
>
> This is correct but incomplete.  Attached is a trivial patch to also
> suggest that the user might have been trying to use a window function.

I think you might have misthought this one. If there's an aggregate
function in the SELECT or HAVING clause, then anything else in the
SELECT clause is going to have to be either in the GROUP BY clause, be
functionally dependent on the GROUP BY clause, or be in an aggregate
function. Putting it into a window function won't help the situation.

postgres=# select sum(x) over(),avg(x) FROM (VALUES (1), (2), (3)) AS v (x);
psql: ERROR:  column "v.x" must appear in the GROUP BY clause or be
used in an aggregate function
LINE 1: select sum(x) over(),avg(x) FROM (VALUES (1), (2), (3)) AS v...
                   ^

If there's any change to make to the error message then it would be to
add the functional dependency part, but since we're pretty bad at
detecting that, I don't think we should.

-- 
 David Rowley                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Vik Fearing
Date:
Subject: Aggregate error message
Next
From: didier
Date:
Subject: Re: [HACKERS] Small fix: avoid passing null pointers to memcpy()