Re: unnesting multirange data types

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Noah Misch <noah(at)leadboat(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Zhihong Yu <zyu(at)yugabyte(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: unnesting multirange data types
Date: 2021-07-10 22:20:21
Message-ID: 20210710222021.GE1301@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Jul 11, 2021 at 01:00:27AM +0300, Alexander Korotkov wrote:
> On Sat, Jul 10, 2021 at 7:34 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> > 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.
>
> True, but I'm a bit uncomfortable about user instances with different
> catalogs but the same catversions. On the other hand, initdb's with
> beta3 or later will be the vast majority among pg14 instances.
>
> Did we have similar precedents in the past?

It seems so.

Note in particular 74ab96a45, which adds a new function with no bump.
Although that one may not be a good precedent to follow, or one that's been
followed recently.

commit 0aac73e6a2602696d23aa7a9686204965f9093dc
Author: Noah Misch <noah(at)leadboat(dot)com>
Date: Mon Jun 14 17:29:37 2021 -0700

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

commit b09a64d602a19c9a3cc69e4bb0f8986a6f5facf4
Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Date: Thu Sep 20 16:06:18 2018 -0400

Add missing pg_description strings for pg_type entries.

commit a4627e8fd479ff74fffdd49ad07636b79751be45
Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Date: Tue Feb 2 11:39:50 2016 -0500

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

commit b852dc4cbd09156e2c74786d5b265f03d45bc404
Author: Bruce Momjian <bruce(at)momjian(dot)us>
Date: Wed Oct 7 09:06:49 2015 -0400

docs: clarify JSONB operator descriptions

commit a80889a7359e720107b881bcd3e8fd47f3874e36
Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Date: Wed Oct 10 12:19:25 2012 -0400

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

commit c246eb5aafe66d5537b468d6da2116c462775faf
Author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Date: Sat Aug 18 16:14:57 2012 -0400

Make use of LATERAL in information_schema.sequences view.

commit 74ab96a45ef6259aa6a86a781580edea8488511a
Author: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Date: Wed Jan 25 13:15:29 2012 -0300

Add pg_trigger_depth() function

commit ddd6ff289f2512f881493b7793853a96955459ff
Author: Bruce Momjian <bruce(at)momjian(dot)us>
Date: Tue Mar 15 11:26:20 2011 -0400

Add database comments to template0 and postgres databases, and improve

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2021-07-10 22:28:39 Re: unnesting multirange data types
Previous Message Alexander Korotkov 2021-07-10 22:00:27 Re: unnesting multirange data types