From: | Jeff Davis <jdavis(at)postgresql(dot)org> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Clarify the result order of unnest(multirange). |
Date: | 2023-10-27 23:06:47 |
Message-ID: | E1qwVuh-002gMH-DN@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
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
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/d014e6cb188664d053cbed87130416617226b373
Modified Files
--------------
doc/src/sgml/func.sgml | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2023-10-28 01:12:14 | pgsql: doc: improve config syncfs wording |
Previous Message | Bruce Momjian | 2023-10-27 23:05:50 | pgsql: doc Improve C GUC-related comments |