Postgres upgrade to 11 worked on primary, but on backup fails

UCS - Univention Corporate Server
#1

Hello!

We just updated to 5.0.5 and the system diagnostics complained that the primary node still runs with PostgreSQL version9.6, so we updated to 11 according to this article.

Afterward, we also updated our backup node to 5.0.5.
We didn’t initially run a system diagnostic again and tried to update to postgres 11 directly, but somethings is not working.

The whole directory under ls -la /var/lib/postgresql/ is empty. Should this be the case?

Does the backup node not have a replicated PostgreSQL database?

#2

Not sure I understand your situation right, but /var/lib/postgresql/ holds a subdirectory 11 on my UCS 5.0-6.

Does the backup node not have a replicated PostgreSQL database?

Correct, there is no automatic replication. Each installation of the univention-postgresql Debian Metapackage is independent.

1 Like
#3

Yes, that was my question if my secondary node should (automatically) also have a subdirectory ‘11’ in var/lib/postgresql/. My primary does, secondary not.

So, this is excepted behavior.

Mastodon