Re: Rethinking representation of partial-aggregate steps - Mailing list pgsql-hackers

From David Rowley
Subject Re: Rethinking representation of partial-aggregate steps
Date
Msg-id CAKJS1f9=GpUn3eLorCM0XJz3BMaUhmXwC0ZX3Xk4q1=q_AXD4w@mail.gmail.com
Whole thread Raw
In response to Re: Rethinking representation of partial-aggregate steps  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Rethinking representation of partial-aggregate steps  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 27 June 2016 at 03:36, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Looking at this in the light of morning, I'm rather strongly tempted to
> invert the sense of the FINALIZE option, so that "simple" mode works out
> as zero, ie, select no options.  Maybe call it SKIPFINAL instead of
> FINALIZE?

Aggref calls this aggpartial, and I was tempted to invert that many
times and make it aggfinalize, but in the end didn't.
It seems nicer to me to keep it as a list of things that are done,
rather than to make one exception to that just so we can have the
simple mode as 0.

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



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Memory leak in Pl/Python
Next
From: Tom Lane
Date:
Subject: Non-text EXPLAIN output for partial aggregation