postgres
diff --git a/‎src/backend/optimizer/path/equivclass.c
Copy file name to clipboardExpand all lines: src/backend/optimizer/path/equivclass.c
+5-3Lines changed: 5 additions & 3 deletions b/‎src/backend/optimizer/path/equivclass.c
Copy file name to clipboardExpand all lines: src/backend/optimizer/path/equivclass.c
+5-3Lines changed: 5 additions & 3 deletions
diff --git a/‎src/backend/optimizer/plan/createplan.c
Copy file name to clipboardExpand all lines: src/backend/optimizer/plan/createplan.c
+3Lines changed: 3 additions & 0 deletions b/‎src/backend/optimizer/plan/createplan.c
Copy file name to clipboardExpand all lines: src/backend/optimizer/plan/createplan.c
+3Lines changed: 3 additions & 0 deletions
@@ -798,9 +798,11 @@ find_em_expr_for_rel(EquivalenceClass *ec, RelOptInfo *rel)
 }
 
 /*
- * Find an equivalence class member expression that can be safely used by a
- * sort node on top of the provided relation. The rules here must match those
- * applied in prepare_sort_from_pathkeys.
+ * Find an equivalence class member expression that can be safely used to build
+ * a sort node using the provided relation. The rules are a subset of those
+ * applied in prepare_sort_from_pathkeys since that function deals with sorts
+ * that must be delayed until the last stages of query execution, while here
+ * we only care about proactive sorts.
  */
 Expr *
 find_em_expr_usable_for_sorting_rel(PlannerInfo *root, EquivalenceClass *ec,
 
@@ -5850,6 +5850,9 @@ make_incrementalsort(Plan *lefttree, int numCols, int nPresortedCols,
  *
  * Returns the node which is to be the input to the Sort (either lefttree,
  * or a Result stacked atop lefttree).
+ *
+ * Note: Restrictions on what expressions are safely sortable may also need to
+ * be added to find_em_expr_usable_for_sorting_rel.
  */
 static Plan *
 prepare_sort_from_pathkeys(Plan *lefttree, List *pathkeys,