On Tue, Mar 22, 2011 at 4:35 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Reimplement planner's handling of MIN/MAX aggregate optimization (again). >
I'm just curious, Why is this no longer an interesting special case? --- this is an interesting special case as of 9.1 -explain (costs off) - select min(unique2) from tenk1 where unique2 = 42; - QUERY PLAN ------------------------------------------------ - Aggregate - -> Index Scan using tenk1_unique2 on tenk1 - Index Cond: (unique2 = 42) -- greg -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
