Re: POC: GROUP BY optimization - Mailing list pgsql-hackers

From jian he
Subject Re: POC: GROUP BY optimization
Date
Msg-id CACJufxHVvFdeLWDfp9MBEUvpizau4Vw83hN8wjOSegeptk5w8A@mail.gmail.com
Whole thread Raw
In response to Re: POC: GROUP BY optimization  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: POC: GROUP BY optimization
List pgsql-hackers
On Fri, May 31, 2024 at 8:12 AM Alexander Korotkov <aekorotkov@gmail.com> wrote:
>
> I've revised some grammar including the sentence you've proposed.
>

-static List *groupclause_apply_groupingset(PlannerInfo *root, List *force);
+static List *preprocess_groupclause(PlannerInfo *root, List *force);

changing preprocess_groupclause the second argument
from "force" to "gset" would be more intuitive, I think.


`elog(ERROR, "Order of group-by clauses doesn't correspond incoming
sort order");`

I think this error message makes people wonder what "incoming sort order" is.
BTW, "correspond", generally people use  "correspond to".


I did some minor cosmetic changes, mainly changing foreach to foreach_node.
Please check the attachment.

Attachment

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: meson and check-tests
Next
From: Pierre Forstmann
Date:
Subject: Re: pltcl crashes due to a syntax error