Re: [HACKERS] Parsing of aggregate ORDER BY clauses

even if it means the function is called with '1' twice) or floatcol::integer (1.1 and 1.2 are not distinct)? I'm guessing the former, even if it means the function is called multiple times with the same final (after typecasting) input value. The latter would only be correct if the

[HACKERS] Planner deficiencies with views that use windowing functions

-> WindowAgg (cost=0.00..625.25 rows=1 width=8) (actual time=0.033..23.904 rows=1 loops=1)" -- "-> Index Scan using numbers_pkey on numbers (cost=0.00..450.25 rows=1 width=8) (actual time=0.017..9.184 rows=1 loops=1)" -- "Total runtime: 46.066 ms" -- c is named in every windowing function's PARTITION BY, thus filtering by it at the view level would have no impact on the actual results returned. -- Thus, this SHOULD optimize just like case 2. -- Daniel Grace AGE, LLC System Administrator and Software Developer -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers