Re: unnesting multirange data types - Mailing list pgsql-hackers

From Justin Pryzby
Subject Re: unnesting multirange data types
Date
Msg-id 20210611233017.GO16435@telsasoft.com
Whole thread Raw
In response to Re: unnesting multirange data types  (Alexander Korotkov <aekorotkov@gmail.com>)
Responses Re: unnesting multirange data types  (Alexander Korotkov <aekorotkov@gmail.com>)
List pgsql-hackers
On Fri, Jun 11, 2021 at 11:37:58PM +0300, Alexander Korotkov wrote:
> On Fri, Jun 11, 2021 at 1:04 AM Justin Pryzby <pryzby@telsasoft.com> wrote:
> >
> > +{ oid => '1293', descr => 'expand mutlirange to set of ranges',
> >
> > typo: mutlirange
> 
> Fixed, thanks.
> 
> The patch with the implementation of both unnest() and cast to array
> is attached.  It contains both tests and docs.

|+   The multirange could be explicitly cast to the array of corresponding
should say: "can be cast to an array of corresponding.."

|+ * Cast multirange to the array of ranges.
I think should be: *an array of ranges

Per sqlsmith, this is causing consistent crashes.
I took one of its less appalling queries and simplified it to this:

select
pg_catalog.multirange_to_array(
    cast(pg_catalog.int8multirange() as int8multirange)) as c2
from (select 1)x;

-- 
Justin



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Fix buffer not null terminated on (ecpg lib)
Next
From: Alexander Korotkov
Date:
Subject: Re: unnesting multirange data types