• Tom Lane's avatar
    When we have successfully optimized a MIN or MAX aggregate into an indexscan, · ff72280c
    Tom Lane authored
    the query result must be exactly one row (since we don't do this when there's
    any GROUP BY).  Therefore any ORDER BY or DISTINCT attached to the query is
    useless and can be dropped.  Aside from saving useless cycles, this protects
    us against problems with matching the hacked-up tlist entries to sort clauses,
    as seen in a bug report from Taiki Yamaguchi.  We might need to work harder
    if we ever try to optimize grouped queries with this approach, but this
    solution will do for now.
    ff72280c
planner.c 56.3 KB