Re: [PATCH] GROUP BY ALL - Mailing list pgsql-hackers

From David Christensen
Subject Re: [PATCH] GROUP BY ALL
Date
Msg-id CAHM0NXgB7hm-JH8c1o=o-4P7LYn_EoE=XZAW0ENdtP-nso60YQ@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] GROUP BY ALL  (David Christensen <david@pgguru.net>)
Responses Re: [PATCH] GROUP BY ALL
List pgsql-hackers
Version 3 of this patch, incorporating some of the feedback thus far:


On Fri, Sep 26, 2025 at 11:56 AM David Christensen <david@pgguru.net> wrote:
>
> On Fri, Sep 26, 2025 at 11:38 AM jian he <jian.universality@gmail.com> wrote:
> >
> > On Fri, Sep 26, 2025 at 11:46 PM David Christensen <david@pgguru.net> wrote:
> > >
> > > >
> > > > I’m interested in picking it up again but would appreciate the review.
> > >
> > > Here is a rebased version with a few more tests.  I also changed the
> > > main check here to using `!contain_agg_clause` instead of
> > > `!IsA(Aggref))` directly.  (This was defined in `optimizer/clauses.h`,
> > > but we already are pulling in `optimizer.h`, so it felt valid to me.)
> > >
> >
> > hi.
> > I only briefly browse the patch text file, so forgive me.
> > seems missing deparse regress tests
> >
> > i think you may need one test like:
> >
> > create view v1 as SELECT b, COUNT(*) FROM t1 GROUP BY ALL;
> > \sv v1
>
> Thanks, good suggestion; not sure the appropriate final location for
> this, but it did show a bug in the current patch.
>
> David

Attachment

pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: Report bytes and transactions actually sent downtream
Next
From: Sami Imseih
Date:
Subject: Re: Add support for entry counting in pgstats