On 06/09/2018 08:09 PM, Tomas Vondra wrote:
>
> /snip/
>
> 4) when adding Sort for grouping, try producing the right output order
> (if the ORDER BY was specified)
>
BTW I've just realized we already do something similar in master. If you
run a query like this:
SELECT a, b, count(*) FROM t GROUP BY b, a ORDER BY a;
we will actually plan it like this:
QUERY PLAN
---------------------------
GroupAggregate
Group Key: a, b
-> Sort
Sort Key: a, b
-> Seq Scan on t
(5 rows)
I.e. we already do reorder the group clauses to match ORDER BY, to only
require a single sort. This happens in preprocess_groupclause(), which
also explains the reasoning behind that.
I wonder if some of the new code reordering group pathkeys could/should
be moved here (not sure, maybe it's too early for those decisions). In
any case, it might be appropriate to update some of the comments before
preprocess_groupclause() which claim we don't do certain things added by
the proposed patches.
This probably also somewhat refutes my claim that the order of grouping
keys is currently fully determined by users (and so they may pick the
most efficient order), while the reorder-by-ndistinct patch would make
that impossible. Apparently when there's ORDER BY, we already mess with
the order of group clauses - there are ways to get around it (subquery
with OFFSET 0) but it's much less clear.
regards
--
Tomas Vondra http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
