RE: Partial aggregates pushdown - Mailing list pgsql-hackers

From Fujii.Yuki@df.MitsubishiElectric.co.jp"
Subject RE: Partial aggregates pushdown
Date
Msg-id TY2PR01MB383583A1AB42A2CDEE49E25495D22@TY2PR01MB3835.jpnprd01.prod.outlook.com
Whole thread Raw
In response to RE: Partial aggregates pushdown  ("Fujii.Yuki@df.MitsubishiElectric.co.jp" <Fujii.Yuki@df.MitsubishiElectric.co.jp>)
List pgsql-hackers
> From: Fujii Yuki <Fujii.Yuki@df.MitsubishiElectric.co.jp>
> Sent: Monday, July 1, 2024 6:42 AM
> Hi hackers.
> 
> On Wed, Jun 5, 2024 at 9:15?AM Fujii.Yuki@df.MitsubishiElectric.co.jp <Fujii.Yuki@df.mitsubishielectric.co.jp>
wrote:
> >   Requirement2. Consider appropriate position of the new keyword "PARTIAL_AGGREGATE". (with Robert)
> >     Existing patch: Before the target expression. Ex. avg(PARTIAL_AGGREGATE c1)
> >     Ideal: Before the aggregate function. Ex. PARTIAL_AGGREGATE avg(c1)
> >   Requirement3. Consider to avoid to make the new keyword "PARTIAL_AGGREGATE" become a reserved word. (with
> Robert)
> >     In the existing patch, "PARTIAL_AGGREGATE" is a reserved word.
> I considered the above two requirement.
> Based on my research, there is no way to use PARTIAL_AGGREGATE in front of a function name without making it a
> reserved word.
With this way, I couldn't resolve shift/reduce conflicts.

pgsql-hackers by date:

Previous
From: "Fujii.Yuki@df.MitsubishiElectric.co.jp"
Date:
Subject: RE: Partial aggregates pushdown
Next
From: Noah Misch
Date:
Subject: Re: MAINTAIN privilege -- what do we need to un-revert it?