Re: unnesting multirange data types

From: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: 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>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Zhihong Yu <zyu(at)yugabyte(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: unnesting multirange data types
Date: 2021-07-10 22:00:27
Message-ID: CAPpHfdsWE0aWtS89r2Jadff-4UcU-=zbg__m+E2RzMWWDmuyVA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

------
Regards,
Alexander Korotkov

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2021-07-10 22:20:21 Re: unnesting multirange data types
Previous Message Magnus Hagander 2021-07-10 20:45:17 Re: Support kerberos authentication for postgres_fdw