| 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:52:49 |
| Message-ID: | e08cc0400901041652t695cf36coc46c9a3bd4253da6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
2009/1/5 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> "Hitoshi Harada" <umi(dot)tanuki(at)gmail(dot)com> writes:
>> 2008/12/31 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>>> RANGE UNBOUNDED PRECEDING -- same as AND CURRENT ROW
>>> ROWS UNBOUNDED PRECEDING -- same as AND CURRENT ROW
>
>> Is this true?
>
> 7.11 syntax rule 9 says so. AFAICS general rule 5b doesn't discuss the
> case where <window frame bound 2> isn't present, and doesn't need to
> because of syntax rule 9.
>
OK, I've just found it and confirmed Oracle does so.
--
Hitoshi Harada
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen R. van den Berg | 2009-01-05 01:30:38 | QuickLZ compression algorithm (Re: Inclusion in the PostgreSQL backend for toasting rows) |
| Previous Message | KaiGai Kohei | 2009-01-05 00:44:49 | Re: generic reloptions improvement |