> It's hardly "general purpose" if it randomly refuses to > sort certain types. I would say it should be able to sort > anything that ORDER BY will handle --- and that certainly > includes the cases shown here.
I wonder how useful / convenient the new function will be considering that we already have CTEs and can do:
SELECT array_agg(x ORDER BY x) FROM unnest(ARRAY[5,1,3,2,4]) AS x;
Perhaps there are use cases I didn't consider?
Succinctness of expression. Plus I'm under the impression that a function doing this is going to be somewhat faster than composing two functions together within a multi-node subtree.
I feel like the same observation could have been made for array_shuffle but we added that. This function being added feels to me like just completing the set.
