Re: Postgres14.1 bug with pg_restore and repmgr
| От | Stanisław Kodzis |
|---|---|
| Тема | Re: Postgres14.1 bug with pg_restore and repmgr |
| Дата | |
| Msg-id | CAMxe1z7_CHiOzfMP3eMU3XKDBxQYLv3js+WNK0ZRJzsDNaa_2g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Postgres14.1 bug with pg_restore and repmgr (Michael Paquier <michael@paquier.xyz>) |
| Ответы |
Re: Postgres14.1 bug with pg_restore and repmgr
|
| Список | pgsql-bugs |
Hi Michael,
Thank you for your feedback and suggestion :)
What do you actually mean by "dropping repmgr extension"? Do you mean 9.6 or 14.1 DB? Do you mean DROP EXTENSION "repmgr" on 9.6?
I commented out in 14.1 postgres.conf:
#shared_preload_libraries = 'repmgr'
But got same error.
FYI, I've created issue with repmgr support for this - https://github.com/EnterpriseDB/repmgr/issues/727
Looking forward to reading from you.
Stanisław
śr., 17 lis 2021 o 03:39 Michael Paquier <michael@paquier.xyz> napisał(a):
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)
> ALTER EXTENSION "repmgr"
> 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
issue..
--
Michael
В списке pgsql-bugs по дате отправления: