| From: | Daniel Farina <drfarina(at)acm(dot)org> |
|---|---|
| To: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Windowing Qual Pushdown |
| Date: | 2010-03-23 08:20:21 |
| Message-ID: | 7b97c5a41003230120y71d58c6cld580b7b222391855@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 23, 2010 at 12:40 AM, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> wrote:
> I believe the changes will probably not be 2-3 lines (ie. a member
> added to Query structure, etc) if I try it. But the optimizer part is
> too complicated to me so that I am not sure, either. My idea above is
> that the similar mechanism you see in GROUP BY optimization will help
Are you suggesting that the windowing clause should perhaps refer to a
column in the target list, much like GROUP BY/ORDER BY, so that one
can easily see if the qual in the fromexpr corresponds to the
windowClause to see if the pushdown is safe?
fdr
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-03-23 08:37:33 | Re: Ragged latency log data in multi-threaded pgbench |
| Previous Message | Pavel Stehule | 2010-03-23 08:04:50 | Re: WIP: preloading of ispell dictionary |