2008/12/30 Tom Lane <t...@sss.pgh.pa.us>: > "Hitoshi Harada" <umi.tan...@gmail.com> writes: >> And surveying sgml docs, I found this is not correct. > >> http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/select.sgml?r1=1.112&r2=1.113 > >> + default framing behavior, which is equivalent to the framing clause >> + <literal>ROWS BETWEEN UNBOUNDED PRECEDING AND CURRENT ROW</>. > >> the default frame with ORDER BY clause is RANGE BETWEEN UNBOUNDED >> PRECEDING AND CURRENT ROW, as aggregates perform rows peer to the >> current row. > > What is the difference? AFAICS the RANGE and ROWS keywords ought to be > equivalent if you are not specifying "expression PRECEDING" or > "expression FOLLOWING".
The difference is that RANGE ... CURRENT ROW contains all peers of the current row, while ROWS ... CURRENT ROW doesn't contain them but the current row itself only. See 7.11 rule 5-b. Regards, -- Hitoshi Harada -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
