From: | David Christensen <david(at)pgguru(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
Subject: | Re: [PATCH] GROUP BY ALL |
Date: | 2025-09-26 15:52:36 |
Message-ID: | CAHM0NXib3ZpAkPypXS6coGrydWadp8NXHvSinOcGF+uOHJs+hQ@mail.gmail.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Sep 26, 2025 at 9:12 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Peter Eisentraut <peter(at)eisentraut(dot)org> writes:
> > The initially proposed patch appears to have the right idea overall.
> > But it does not handle more complex cases like
> > SELECT a, SUM(b)+a FROM t1 GROUP BY ALL;
>
> > (For explanation: GROUP BY ALL expands to all select list entries that
> > do not contain aggregates. So the above would expand to
> > SELECT a, SUM(b)+a FROM t1 GROUP BY a;
> > which should then be rejected based on the existing rules.)
>
> I thought I understood this definition, up till your last
> comment. What's invalid about that expanded query?
>
> regression=# create table t1 (a int, b int);
> CREATE TABLE
> regression=# SELECT a, SUM(b)+a FROM t1 GROUP BY a;
> a | ?column?
> ---+----------
> (0 rows)
Agreed that this shouldn't be an error; added a similar test case to
v2 of this patch.
David
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2025-09-26 15:54:18 | Re: [PATCH] GROUP BY ALL |
Previous Message | Jacob Champion | 2025-09-26 15:51:26 | Re: test_json_parser/002_inline is kind of slow |