Re: unnesting multirange data types

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: "Jonathan S. Katz" <jkatz@postgresql.org>, Justin Pryzby <pryzby@telsasoft.com>, Zhihong Yu <zyu@yugabyte.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-06-19T16:35:26Z
Lists: pgsql-hackers
Alexander Korotkov <aekorotkov@gmail.com> writes:
> Patch successfully passed commitfest.cputube.org.  I'm going to
> re-push it if there are no objections.

I'm still not happy about the way you've done the multirange-to-array
part.  I think we'd be better off improving the polymorphism rules so
that that can be handled by one polymorphic function.  Obviously that'd
be a task for v15, but we've already concluded that just having the
unnest ability would be minimally sufficient for v14.

So I think you should trim it down to just the unnest part.

In any case, beta2 wraps on Monday, and there is very little time
left for a full round of buildfarm testing.  I almost feel that
it's too late to consider pushing this today.  Tomorrow absolutely
is too late for beta2.

			regards, tom lane



Commits

  1. Fix small inconsistencies in catalog definition of multirange operators

  2. Revert 29854ee8d1 due to buildfarm failures

  3. Copy-edit text for the pg_terminate_backend() "timeout" parameter.

  4. Add missing pg_description strings for pg_type entries.

  5. Fix pg_description entries for jsonb_to_record() and jsonb_to_recordset().

  6. docs: clarify JSONB operator descriptions

  7. Set procost to 10 for each of the pg_foo_is_visible() functions.

  8. Make use of LATERAL in information_schema.sequences view.

  9. Add pg_trigger_depth() function

  10. Add database comments to template0 and postgres databases, and improve