From: | Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com> |
---|---|
To: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: add more frame types in window functions (ROWS) |
Date: | 2009-12-05 10:17:59 |
Message-ID: | e08cc0400912050217u25bb9f3fq58fbe1d21bd9cd6@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2009/12/5 Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>:
> I'm now reworking as reviewed. The last issue is whether we accept
> extension of frame types without RANGE support.
Attached is updated version. I added AggGetMemoryContext() in
executor/nodeAgg.h (though I'm not sure where to go...) and its second
argument "iswindowagg" is output parameter to know whether the call
context is Agg or WindowAgg. Your proposal of APIs to know whether the
function is called as Aggregate or not is also a candidate to be, but
it seems out of this patch scope, so it doesn't touch anything.
Fix tsearch function is also included, as well as typo phisical ->
physical. Pass false to get_rule_expr() of value in
PRECEDING/FOLLOWING.
One thing for rule test, I checked existing regression test cases and
concluded DROP VIEW is necessary, or even VIEW test for a specific
feature is not needed. I remember your aggregate ORDER BY patch
contains "rules" test changes. However, since processing order of
regression tests is not predictable and may change AFAIK, I guess it
shouldn't add those changes in rules.out.
Regards.
--
Hitoshi Harada
Attachment | Content-Type | Size |
---|---|---|
rows_frame_types.20091205.patch.gz | application/x-gzip | 18.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Gierth | 2009-12-05 10:53:35 | Re: add more frame types in window functions (ROWS) |
Previous Message | Simon Riggs | 2009-12-05 09:51:23 | Re: Summary and Plan for Hot Standby |