public inbox for [email protected]
help / color / mirror / Atom feedFrom: Tomas Vondra <[email protected]>
Subject: [PATCH 8/8] fix
Date: Thu, 19 Mar 2020 18:48:19 +0100
---
src/backend/optimizer/plan/planner.c | 16 +++++++---------
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/src/backend/optimizer/plan/planner.c b/src/backend/optimizer/plan/planner.c
index 2880fcabe8..b4763e79f8 100644
--- a/src/backend/optimizer/plan/planner.c
+++ b/src/backend/optimizer/plan/planner.c
@@ -5100,17 +5100,17 @@ create_ordered_paths(PlannerInfo *root,
double total_groups;
/*
- * We don't care if this is the cheapest partial path - we
- * can't simply skip it, because it may be partially sorted in
- * which case we want to consider incremental sort on top of
- * it (instead of full sort, which is what happens above).
+ * We don't care if this is the cheapest partial path - we can't
+ * simply skip it, because it may be partially sorted in which
+ * case we want to consider adding incremental sort (instead of
+ * full sort, which is what happens above).
*/
is_sorted = pathkeys_common_contained_in(root->sort_pathkeys,
input_path->pathkeys,
&presorted_keys);
- /* Ignore already sorted paths */
+ /* No point in adding incremental sort on fully sorted paths. */
if (is_sorted)
continue;
@@ -7005,9 +7005,7 @@ create_partial_grouping_paths(PlannerInfo *root,
}
}
- /*
- * Also consider incremental sort on all partially sorted paths.
- */
+ /* Consider incremental sort on all partial paths, if enabled. */
if (enable_incrementalsort)
{
foreach(lc, input_rel->pathlist)
@@ -7122,10 +7120,10 @@ create_partial_grouping_paths(PlannerInfo *root,
/* We've already skipped fully sorted paths above. */
Assert(!is_sorted);
+ /* no shared prefix, not point in building incremental sort */
if (presorted_keys == 0)
continue;
- /* Since we have presorted keys, consider incremental sort. */
path = (Path *) create_incremental_sort_path(root,
partially_grouped_rel,
path,
--
2.21.1
--dfcjsgdukgytabqd--
view thread (8+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: [PATCH 8/8] fix
In-Reply-To: <no-message-id-1882718@localhost>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox