rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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
This commit is contained in:
Jeff Davis 2023-10-27 15:21:42 -07:00
parent 12cf3ac7f3
commit d014e6cb18
1 changed files with 1 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
doc/src/sgml/func.sgml
View File

@ -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>