Re: unnest multirange, returned order

From: Daniel Fredouille <daniel(dot)fredouille(at)gmail(dot)com>
To: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
Cc: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: unnest multirange, returned order
Date: 2023-10-13 19:33:57
Message-ID: CAEpV6kUr-7aS6v-azW3eeaw7p0r-xZzk4FtcNEN8HM13Orfc9g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

Hi,

sorry it took me some time to reply. Yes, the patch is perfect if this is
indeed the behavior.

cheers
Daniel

Le jeu. 5 oct. 2023 à 02:50, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> a
écrit :

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

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Tom Lane 2023-10-13 20:37:53 Re: Clarify: default precision on timestamps is 6
Previous Message Kirk Parker 2023-10-13 17:24:14 Re: Clarify: default precision on timestamps is 6

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2023-10-13 20:23:21 Re: should frontend tools use syncfs() ?
Previous Message Jeff Davis 2023-10-13 18:54:07 Re: Questions about the new subscription parameter: password_required