Re: [HACKERS] More frame options in window functions
2010/1/5 Hitoshi Harada umi.tan...@gmail.com: 2009/12/31 Hitoshi Harada umi.tan...@gmail.com: Attached is the fix pointed out in the previous CommitFest plus RANGE offset support. Improved version attached. In this revision I fixed type mismatch case like ORDER BY int4_data RANGE BETWEEN int8_data PRECEDING Update of comments and fix typos in documents are also included. Fix some trivial things and synced with HEAD. I've came up with using upper and lower instead of start and end for window frame bounds. The upper/lower is more beautiful since two have same length but start/end is used since it was introduced. Comments? Regards, -- Hitoshi Harada more_frame_options.20100113.patch.gz Description: GNU Zip compressed data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] More frame options in window functions
2009/12/31 Hitoshi Harada umi.tan...@gmail.com: Attached is the fix pointed out in the previous CommitFest plus RANGE offset support. Improved version attached. In this revision I fixed type mismatch case like ORDER BY int4_data RANGE BETWEEN int8_data PRECEDING Update of comments and fix typos in documents are also included. Regards, -- Hitoshi Harada more_frame_options.20100105.patch.gz Description: GNU Zip compressed data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] More frame options in window functions
Attached is the fix pointed out in the previous CommitFest plus RANGE offset support. *fix - move window regression test to another parallel group, but regarding the limitation of 20 per group the union test goes to the group the window test belonged to. - allow NULL iswindowagg as an argument of AggGetMemoryContext - change view name to longer one *RANGE offset - allow all of RANGE BETWEEN value PRECEDING/FOLLOWING AND value PRECEDING/FOLLOWING for any data types that support ORDER BY and additions/subtractions, which is extended design to the spec. The spec says data types allowed in RANGE offset are only numeric and temporal ones but we don't have such limitation. - add +/- operator search code in parsing, which is used to calculate frame bound, but I'm not sure if this is right approach. - add more regression tests Regards, -- Hitoshi Harada more_frame_options.20091231.patch.gz Description: GNU Zip compressed data -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
