diff options
author | Alexander Korotkov <akorotkov@postgresql.org> | 2024-06-06 13:44:34 +0300 |
---|---|---|
committer | Alexander Korotkov <akorotkov@postgresql.org> | 2024-06-06 13:44:34 +0300 |
commit | 505c008ca37c4f6f2fffcde370b5d8354c4d4dc3 (patch) | |
tree | 7c1f2ac7180cb5e994e77d9a08fa98842ed22075 /contrib/postgres_fdw/postgres_fdw.c | |
parent | 0c1af2c35c7b456bd2fc76bbc9df5aa9c7911bde (diff) | |
download | postgresql-505c008ca37c4f6f2fffcde370b5d8354c4d4dc3.tar.gz postgresql-505c008ca37c4f6f2fffcde370b5d8354c4d4dc3.zip |
Restore preprocess_groupclause()
0452b461bc made optimizer explore alternative orderings of group-by pathkeys.
It eliminated preprocess_groupclause(), which was intended to match items
between GROUP BY and ORDER BY. Instead, get_useful_group_keys_orderings()
function generates orderings of GROUP BY elements at the time of grouping
paths generation. The get_useful_group_keys_orderings() function takes into
account 3 orderings of GROUP BY pathkeys and clauses: original order as written
in GROUP BY, matching ORDER BY clauses as much as possible, and matching the
input path as much as possible. Given that even before 0452b461b,
preprocess_groupclause() could change the original order of GROUP BY clauses
we don't need to consider it apart from ordering matching ORDER BY clauses.
This commit restores preprocess_groupclause() to provide an ordering of
GROUP BY elements matching ORDER BY before generation of paths. The new
version of preprocess_groupclause() takes into account an incremental sort.
The get_useful_group_keys_orderings() function now takes into 2 orderings of
GROUP BY elements: the order generated preprocess_groupclause() and the order
matching the input path as much as possible.
Discussion: https://postgr.es/m/CAPpHfdvyWLMGwvxaf%3D7KAp-z-4mxbSH8ti2f6mNOQv5metZFzg%40mail.gmail.com
Author: Alexander Korotkov
Reviewed-by: Andrei Lepikhov, Pavel Borisov
Diffstat (limited to 'contrib/postgres_fdw/postgres_fdw.c')
0 files changed, 0 insertions, 0 deletions