| From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
|---|---|
| To: | heikki(dot)linnakangas(at)enterprisedb(dot)com (Heikki Linnakangas), pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Aggregate ORDER BY patch |
| Date: | 2009-11-13 18:02:05 |
| Message-ID: | 87k4xupbl1.fsf@news-spur.riddles.org.uk |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>>>> "Heikki" == Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>> No artificial restrictions are imposed on what syntactical
>> combinations are allowed. However, ORDER BY is not allowed with
>> aggregates used as window functions (as per the existing
>> restriction on DISTINCT).
Heikki> How is this different from window functions?
Window functions return a row for each row of input, aggregates don't.
The reason I didn't tackle the case of aggregate functions used as
window functions is that the spec allows constructs like this:
array_agg(a order by b) over (order by c)
which can't be represented using the aggregate-as-window-function
mechanism as it currently stands, since you'd have to re-sort the
window each time.
--
Andrew (irc:RhodiumToad)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-11-13 18:04:08 | Re: next CommitFest |
| Previous Message | Peter Eisentraut | 2009-11-13 17:57:04 | Re: cvs head doesn't pass make check on one of the machines here |