Clarify the result order of unnest(multirange).

jeff-davis · pull[bot] · commit cc12f49df6fb · 2024-01-24T15:43:36.000Z
It is best not to mention the storage order, because that is an implementation detail and has confused at least one user, who assumed that the storage order is the order in which the constituent ranges were written in SQL. Since the sorting order is explained at the beginning of the page, it should be sufficient to say that the ranges are returned in ascending order. Author: Laurenz Albe Reviewed-by: Daniel Fredouille Discussion: https://postgr.es/m/169627213477.3727338.17653654241633692682%40wrigleys.postgresql.org
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml
@@ -20218,8 +20218,7 @@ SELECT NULLIF(value, '(none)') ...
         <returnvalue>setof anyrange</returnvalue>
        </para>
        <para>
-        Expands a multirange into a set of ranges.
-        The ranges are read out in storage order (ascending).
+        Expands a multirange into a set of ranges in ascending order.
        </para>
        <para>
         <literal>unnest('{[1,2), [3,4)}'::int4multirange)</literal>
