You are not logged in.
Pages: 1
Hi all,
I recently updated my system. I then needed to use postgres locally, which I did not have to do for some time.
Of course, posgres needed to be upgraded. However, it turns out that I need to upgrade by two major versions.
So of course the `pg_update` command from the forum fails, because `opt/pgsql-*/bin` does not exist.
(Did the update instructions change? I remember it working previously..)
Installing `postgresql-old-update` does not work because it is not old enough (specifically, running `pg_update` complains that the versions are mismatched).
Downgrading to an older version of `postgresql-old-update` fails because the binary refuse to execute with the updated libicu:
/opt/pgsql-13/bin/postgres: error while loading shared libraries: libicui18n.so.72: cannot open shared object file: No such file or directory
Building `postgresql-13-update` from the AUR fails because of even more libicu issues:
/usr/src/debug/postgresql-13-upgrade/postgresql-13.10/src/backend/access/hash/hashfunc.c:301: undefined reference to `ucol_getSortKey_66'
/usr/bin/ld: /usr/src/debug/postgresql-13-upgrade/postgresql-13.10/src/backend/access/hash/hashfunc.c:304: undefined reference to `ucol_getSortKey_66'
My specific question is "How do I update the cluster now?" My more general question is "Why can you not statically link postgresql-old-update?"
Thanks!
Offline
Was the system fully updated when you had the issue building postgresql-13-update? As I just built that package locally in a clean chroot without issue. I would suggest you try building it the same way.
Offline
Pages: 1