| From: | Noah Misch <noah(at)leadboat(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: unnesting multirange data types |
| Date: | 2021-06-20 08:09:21 |
| Message-ID: | 20210620080921.GB1285871@rfd.leadboat.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Jun 19, 2021 at 10:05:09PM -0400, Tom Lane wrote:
> Alexander Korotkov <aekorotkov(at)gmail(dot)com> writes:
> > I also don't feel comfortable hurrying with unnest part to beta2.
> > According to the open items wiki page, there should be beta3. Does
> > unnest part have a chance for beta3?
>
> Hm. I'd prefer to avoid another forced initdb after beta2. On the
> other hand, it's entirely likely that there will be some other thing
> that forces that; in which case there'd be no reason not to push in
> the unnest feature as well.
>
> I'd say let's sit on the unnest code for a little bit and see what
> happens.
I think $SUBJECT can't simultaneously offer too little to justify its own
catversion bump and also offer enough to bypass feature freeze. If multirange
is good without $SUBJECT, then $SUBJECT should wait for v15. Otherwise, the
matter of the catversion bump should not delay commit of $SUBJECT.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2021-06-20 09:02:14 | Re: pgbench logging broken by time logic changes |
| Previous Message | Thomas Munro | 2021-06-20 07:38:50 | Re: pgbench logging broken by time logic changes |