| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
| Cc: | "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 02:05:09 |
| Message-ID: | 1445102.1624154709@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-06-20 03:18:35 | Re: pgbench logging broken by time logic changes |
| Previous Message | Alexander Korotkov | 2021-06-20 01:12:56 | Re: unnesting multirange data types |