Re: unnesting multirange data types

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: unnesting multirange data types
Date: 2021-06-10 19:08:21
Message-ID: CAPpHfdvZ00N=7JK6XMXGeETiFdDjoYHGbHOAuNeNLsaU4khsGQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jun 10, 2021 at 8:57 PM Jonathan S. Katz <jkatz(at)postgresql(dot)org> wrote:
> On 6/10/21 1:24 PM, Alexander Korotkov wrote:
> > I agree that unnest(), cast to array and subscription are missing
> > points. Proper subscription support requires expanded object
> > handling. And that seems too late for v14.
>
> Agreed, the subscripting functionality is too late for v14. (Though
> perhaps someone ambitious could bridge that gap temporarily with the
> ability to add subscripting to types!).
>
> > But unnset() and cast to
> > array seems trivial. I've drafted unnest support (attached). I'm
> > going to add also cast to the array, tests, and docs within a day.
> > Stay tuned :)
>
> Awesome. I'll defer to others on the implementation. I'll try to test
> out the patch in a bit to see how it works.

Good!

> Are there any objections adding this as a v14 open item?

No objections, let's add it.

------
Regards,
Alexander Korotkov

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Gibson (DB Administrator) 2021-06-10 19:29:05 Re: AWS forcing PG upgrade from v9.6 a disaster
Previous Message Tom Lane 2021-06-10 18:50:52 Re: logical replication of truncate command with trigger causes Assert