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

From Tom Lane
Subject Re: unnesting multirange data types
Date
Msg-id 429332.1623779540@sss.pgh.pa.us
Whole thread Raw
In response to Re: unnesting multirange data types  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: unnesting multirange data types  ("Jonathan S. Katz" <jkatz@postgresql.org>)
Re: unnesting multirange data types  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> On 2021-Jun-15, Tom Lane wrote:
>> I think this ought to be reverted and reviewed more carefully.

> It seems to me that removing the cast-to-range[] is a sufficient fix,
> and that we can do with only the unnest part for pg14; the casts can be
> added in 15 (if at all).  That would mean reverting only half the patch.

Might be a reasonable solution.  But right now I'm annoyed that the
buildfarm is broken, and I'm also convinced that this didn't get
adequate testing.  I think "revert and reconsider" is the way
forward for today.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PATCH] Fix buffer not null terminated on (ecpg lib)
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] Fix buffer not null terminated on (ecpg lib)