Re: Postgres14.1 bug with pg_restore and repmgr

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Stanisław Kodzis <stanislawk(at)ntropy(dot)pl>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Postgres14.1 bug with pg_restore and repmgr
Date: 2021-11-17 02:38:55
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

On Tue, Nov 16, 2021 at 09:34:33AM +0100, Stanisław Kodzis wrote:
> There was 14.1 couple days ago and it affected my upgrade from 9.6 to 14.
> On 14.0 there was smooth upgrade - now after apt upgrade to 14.1 I have the
> error(with pg_upgrade cmd on ubuntu 20.4):

There has been no changes related to extensions between 14.0 and 14.1
AFAIK, so that looks like an issue with the extension shipped in
repmgr and its packaging.

> I dunno how to implement this (on 9.6 is already registered)
> If I register it on 14.1 pg_upgrade won't allow me to continue upgrade.

If you want to speed up things, one thing you could do is perhaps drop
the extension before the upgrade and re-create it on the new cluster
once you are done with pg_upgrade? It is not uncommon to have
post-upgrade reconfigurations depending on what you are doing. This
one is a bit extreme, and it may not work if that's a packaging

In response to


Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2021-11-17 07:01:19 Re: pg_upgrade test for binary compatibility of core data types
Previous Message Дмитрий Иванов 2021-11-17 02:06:25 Re: pg_restore depending on user functions