Postgres Flex repmgr warnings after image update to 0.0.43

[shugel]

I’ve just updated my Postgres Flex cluster from 0.0.42 to 0.0.43

I now get constant warnings:

2023-07-27T11:14:53.629 app[4d8902da6e2328] lhr [info] postgres | 2023-07-27 11:14:53.628 UTC [689] WARNING: database “repmgr” has a collation version mismatch

2023-07-27T11:14:53.629 app[4d8902da6e2328] lhr [info] postgres | 2023-07-27 11:14:53.628 UTC [689] DETAIL: The database was created using collation version 2.31, but the operating system provides version 2.36.

2023-07-27T11:14:53.629 app[4d8902da6e2328] lhr [info] postgres | 2023-07-27 11:14:53.628 UTC [689] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE repmgr REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.

What can I do to fix this?

[lubien]

Hi @shugel

A community member posted a tutorial here:

postgres-flex: database "postgres" has a collation version mismatch

Just recently a new release of postgres-flex was published. Because the Debian version of the base image has been updated, you may see a message like this: database [DATABASE NAME] has a collation version mismatch. There are a few things you need to do here, but in many cases you should be able to resolve this in the following steps: Update the app’s image to the latest available version: fly image update ... List all available databases: postgres=# \l If you’re not sure about the backsl…

Hope this helps