diff options
| author | Jeff Davis | 2023-10-27 22:21:42 +0000 |
|---|---|---|
| committer | Jeff Davis | 2023-10-27 23:06:12 +0000 |
| commit | d014e6cb188664d053cbed87130416617226b373 (patch) | |
| tree | 1cb9bdae2b8cf3f37658022890f7136b0acaa3fb | |
| parent | 12cf3ac7f328ac439a8eca2bfb7771fb6a4f3aa3 (diff) | |
Clarify the result order of unnest(multirange).
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
| -rw-r--r-- | doc/src/sgml/func.sgml | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 7c3e940afef..c76ec52c557 100644 --- 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> |