From: | "Hitoshi Harada" <umi(dot)tanuki(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "David Rowley" <dgrowley(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: WIP patch for basic window frame support |
Date: | 2009-01-05 00:16:23 |
Message-ID: | e08cc0400901041616t279627c4u85ded78d4b6d8efc@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2008/12/31 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> No docs or regression tests yet, but it seems to work ... please check
> against Oracle and DB2 behavior. Supported cases are
>
> RANGE UNBOUNDED PRECEDING -- same as AND CURRENT ROW
> ROWS UNBOUNDED PRECEDING -- same as AND CURRENT ROW
Is this true?
I guess that the 7.11 rule 5.b in the spec says as far as the bound is
not specified in the window frame clause, all rows of the partition
are contained in the frame. The rule then removes rows from the
initial frame as the frame bound indicates.
So as the result,
RANGE UNBOUNDED PRECEDING
ROWS UNBOUNDED PRECEDING
both mean
(RANGE / ROWS) BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING
if I don't miss something.
Regards,
--
Hitoshi Harada
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-01-05 00:34:53 | Re: WIP patch for basic window frame support |
Previous Message | Tom Lane | 2009-01-04 23:37:08 | Re: generic reloptions improvement |