| From: | Tomas Vondra <tv(at)fuzzy(dot)cz> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] aggregate returning anyarray and 'cannot determine result data type' |
| Date: | 2014-04-25 21:16:01 |
| Message-ID: | 535AD091.4060007@fuzzy.cz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On 23.4.2014 16:07, Tom Lane wrote:
>
> To be concrete: let's add a new boolean parameter with the semantics
> of "final function takes extra dummy arguments" (default false).
> There would need to be one for the separate moving-aggregate final
> function too, of course.
>
> The best naming idea I've got right now is "finalfunc_extra" and
> "mfinalfunc_extra", but maybe somebody can do better?
Do we really need a separate parameter for this? Couldn't this be
decided simply using the signature of the final function? Either it has
a single parameter (current behavior), or it has the same parameters as
the state transition function (new behavior).
regards
Tomas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-04-25 21:26:22 | Re: [GENERAL] aggregate returning anyarray and 'cannot determine result data type' |
| Previous Message | Joe Conway | 2014-04-25 16:41:52 | Re: Return and sql tuple descriptions are incompatible |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-04-25 21:17:10 | Re: Expression indexes ignore typmod of expression |
| Previous Message | Tom Lane | 2014-04-25 21:05:26 | Expression indexes ignore typmod of expression |