Re: unnest multirange, returned order

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-04 07:20:16
Message-ID: 47e801481db9947c4a597575ad45e1c6304130ca.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs pgsql-hackers

On Tue, 2023-10-03 at 20:40 -0400, Daniel Fredouille wrote:
> > I'd say that the storag order is the order in which PostgreSQL stores
> > multiranges internally:
>
> Right, I believe that you are right but then this information is not useful for the developer. 
> If storage order is always ascending by range order then let's make it clear,
> if order cannot be counted upon as it may evolve from postgres version to version,
> then let's make it clear as well. WDYT ?

I personally think that it is clear as it is written now.

If you have a good suggestion for an improvement, you could send it;
perhaps someone will pick it up.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message PG Doc comments form 2023-10-04 14:24:11 Unclear guarantees about sort order on https://www.postgresql.org/docs/current/queries-order.html
Previous Message Daniel Fredouille 2023-10-04 00:40:40 Re: unnest multirange, returned order

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2023-10-04 07:34:15 Re: Removing unneeded self joins
Previous Message Andrei Lepikhov 2023-10-04 06:55:59 Re: Removing unneeded self joins