How to fix postgres collations in container?

[digdilem-work]

After applying today's security patches, the logs show warnings like this. These seem to be things that should be addressed.

Can someone please give me a pointer in how to do this? There's no pgsql command available in the container, although there is a postgres user, and if spacewalk-sql is the tool, then I can't hit upon the right commands.

I was thinking something like this once I could get a db shell

\c uyuni
REINDEX DATABASE uyuni;
ALTER DATABASE uyuni REFRESH COLLATION VERSION;
\c reportdb
REINDEX DATABASE reportdb;
ALTER DATABASE reportdb REFRESH COLLATION VERSION;

Thanks

11:31AM ??? Schema update...
11:31AM ??? WARNING:  database "uyuni" has a collation version mismatch
DETAIL:  The database was created using collation version 2.31, but the operating system provides version 2.38.
HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE uyuni REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
11:31AM ??? WARNING:  database "reportdb" has a collation version mismatch
DETAIL:  The database was created using collation version 2.31, but the operating system provides version 2.38.
HINT:  Rebuild all objects in this database that use the default collation and run ALTER DATABASE reportdb REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.