| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Alexander Korotkov <aekorotkov(at)gmail(dot)com>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Zhihong Yu <zyu(at)yugabyte(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: unnesting multirange data types |
| Date: | 2021-06-15 17:52:20 |
| Message-ID: | 429332.1623779540@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-06-15 17:53:08 | Re: [PATCH] Fix buffer not null terminated on (ecpg lib) |
| Previous Message | Andres Freund | 2021-06-15 17:28:58 | Re: [PATCH] Fix buffer not null terminated on (ecpg lib) |