| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Daniel Fredouille <daniel(dot)fredouille(at)gmail(dot)com> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: unnest multirange, returned order |
| Date: | 2023-10-05 06:50:24 |
| Message-ID: | fd85a22502ce44458bc3ddc616bf352c077e67f4.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs pgsql-hackers |
On Wed, 2023-10-04 at 20:12 -0400, Daniel Fredouille wrote:
> unnest ( anymultirange ) → setof anyrange
> Expands a multirange into a set of ranges. The ranges are read out in storage order (ascending) and therefore order cannot be relied upon.
That's not true. The order is deterministic and can be relied on.
How about the attached patch, which does away with the confusing
mention of "storage order"?
Yours,
Laurenz Albe
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Clarify-the-result-order-of-unnest-multirange.patch | text/x-patch | 1.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2023-10-05 14:05:33 | This is too implicit that recovery.signal will be removed |
| Previous Message | Erik Wienhold | 2023-10-05 01:35:27 | Re: Unclear guarantees about sort order on https://www.postgresql.org/docs/current/queries-order.html |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andy Fan | 2023-10-05 06:53:05 | Re: Extract numeric filed in JSONB more effectively |
| Previous Message | Drouvot, Bertrand | 2023-10-05 06:46:48 | Re: Add a new BGWORKER_BYPASS_ROLELOGINCHECK flag |