EnterpriseDB/repmgr

repmgr 5.2 -> 5.3 extension upgrade fails (could not find function "repmgr_set_local_node_id")

Closed this issue · 2 comments

MannerMan commented

Hi,

I have several postgresql clusters running postgres version 10, 12, 13 on Rocky Linux 8. Postgres is installed from postgres yum repo, and repmgr from 2ndquadrant's repo.

I'm attempting an upgrade from repmgr 5.2.1 to 5.3.1, using the following steps

  1. stopping & disabling repmgrd
  2. yum upgrade of the repmgr package from 5.2.1 to 5.3.1
  3. systemctl daemon-reload
  4. (no restart of postgres here since release notes does not state it's required, unlike 5.1 upgrade)
  5. ALTER EXTENSION repmgr UPDATE;
    The ALTER EXTENSION fails with;
Cannot execute SQL 'ALTER EXTENSION repmgr UPDATE;' None: could not find function "repmgr_set_local_node_id" in file "/usr/pgsql-13/lib/repmgr.so"

Restarting postgres and attempting ALTER EXTENSION repmgr UPDATE; again succeeds.

Is a restart supposed to be required when upgrading 5.2 to 5.3? I'm guessing this could be the culprit;

repmgrd: rename internal shared library functions to minimize the risk of clashes with other shared libraries.
This does not affect user-facing SQL functions. However an upgrade of the installed extension version is required.

ibarwick commented

Yes, a restart is required. We are updating the release notes to mention this.

martinmarques commented

Closing as this has been solved already