Re: unnesting multirange data types

Alvaro Herrera <alvherre@alvh.no-ip.org>

From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Noah Misch <noah@leadboat.com>, Tom Lane <tgl@sss.pgh.pa.us>, "Jonathan S. Katz" <jkatz@postgresql.org>, Justin Pryzby <pryzby@telsasoft.com>, Zhihong Yu <zyu@yugabyte.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2021-07-10T16:34:19Z
Lists: pgsql-hackers
On 2021-Jun-27, Alexander Korotkov wrote:

> BTW, I found some small inconsistencies in the declaration of
> multirange operators in the system catalog.  Nothing critical, but if
> we decide to bump catversion in beta3, this patch is also nice to
> push.

Hmm, I think you should push this and not bump catversion.  That way,
nobody is forced to initdb if we end up not having a catversion bump for
some other reason; but also anybody who initdb's with beta3 or later
will get the correct descriptions.

If you don't push it, everybody will have the wrong descriptions.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/



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