| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
| Cc: | Joshua Tolley <eggyknap(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: GROUPING SETS revisited |
| Date: | 2010-08-18 09:43:37 |
| Message-ID: | AANLkTi=QMFmABuH1Wky+X3QV42v2qzP6a7u0EPBMbwTu@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello
I found a break in GROUPING SETS implementation. Now I am playing with
own executor and planner node and I can't to go forward :(. Probably
this feature will need a significant update of our agg implementation.
Probably needs a some similar structure like CTE but it can be a
little bit reduced - there are a simple relation between source query
and result query - I am not sure, if this has to be implemented via
subqueries? The second question is relative big differencies between
GROUP BY behave and GROUP BY GROUPING SETS behave. Now I don't know
about way to join GROUP BY and GROUPING SETS together
Any ideas welcome
Regards
Pavel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-08-18 11:40:04 | Re: security label support, part.2 |
| Previous Message | Magnus Hagander | 2010-08-18 09:13:15 | Re: git: uh-oh |