From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Daniel Fredouille <daniel.fredouille@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: unnest multirange, returned order
Date: Wed, 04 Oct 2023 09:20:16 +0200
Message-ID: <47e801481db9947c4a597575ad45e1c6304130ca.camel@cybertec.at> (raw)
In-Reply-To: <CAEpV6kX9PJAuQ_=5c7ZxCSASu76hkvGfVvwU6WkHTRXzApknfQ@mail.gmail.com>
References: <169627213477.3727338.17653654241633692682@wrigleys.postgresql.org>
<2bad53942920d2e501661af4cd49d6644a22b801.camel@cybertec.at>
<CAEpV6kX9PJAuQ_=5c7ZxCSASu76hkvGfVvwU6WkHTRXzApknfQ@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: laurenz.albe@cybertec.at, daniel.fredouille@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: unnest multirange, returned order
In-Reply-To: <47e801481db9947c4a597575ad45e1c6304130ca.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox