Re: Eager aggregation, take 3
От | Robert Haas |
---|---|
Тема | Re: Eager aggregation, take 3 |
Дата | |
Msg-id | CA+Tgmoa5WbO+GbmZtb6Y1-J75EA6poGjsQHFYR62_N0iQzGMCA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Eager aggregation, take 3 (Richard Guo <guofenglinux@gmail.com>) |
Ответы |
Re: Eager aggregation, take 3
|
Список | pgsql-hackers |
On Sun, Nov 10, 2024 at 7:52 PM Richard Guo <guofenglinux@gmail.com> wrote: > Hmm, currently we only consider grouped aggregation for eager > aggregation. For grouped aggregation, the window function's > arguments, as well as the PARTITION BY expressions, must appear in the > GROUP BY clause. That is to say, the depname column in the first > query, or the n column in the second query, will not be aggregated > into the partial groups. Instead, they will remain as they are as > input for the WindowAgg nodes. It seems to me that this ensures > that we're good with window functions. But maybe I'm wrong. Returning to this point now that I understand what you meant by grouped aggregation: I still don't understand how you expect to be able to evaluate functions like LEAD() and LAG() if any form of partial aggregation has been done. -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: