Re: Aggregate function API versus grouping sets - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Aggregate function API versus grouping sets
Date
Msg-id 18963.1404326824@sss.pgh.pa.us
Whole thread Raw
In response to Re: Aggregate function API versus grouping sets  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Responses Re: Aggregate function API versus grouping sets  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
Re: Aggregate function API versus grouping sets  (Andrew Gierth <andrew@tao11.riddles.org.uk>)
List pgsql-hackers
Andrew Gierth <andrew@tao11.riddles.org.uk> writes:
> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:
>  Tom> Another approach would be to remove AggGetPerAggEContext as such
>  Tom> from the API altogether, and instead offer an interface that
>  Tom> says "register an aggregate cleanup callback", leaving it to the
>  Tom> agg/window core code to figure out which context to hang that
>  Tom> on.  I had thought that exposing this econtext and the
>  Tom> per-input-tuple one would provide useful generality, but maybe
>  Tom> we should rethink that.

> Works for me.

If we're going to do that, I think it needs to be in 9.4.  Are you
going to work up a patch?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: log_error_verbosity and unexpected errors
Next
From: Fujii Masao
Date:
Subject: Re: alter user set local_preload_libraries.