Last two updates (maybe more I dont know) have database mismatch reported in postgressql

[vw-kombi]

This is on unraid container. I noticed it a few days back, then another postgres update, and still there.

.
2025-11-06 18:14:50.061 AEST [1044] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE jfstat REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
2025-11-06 18:15:10.090 AEST [1045] WARNING: database "postgres" has a collation version mismatch
2025-11-06 18:15:10.090 AEST [1045] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2025-11-06 18:15:10.090 AEST [1045] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
2025-11-06 18:15:30.354 AEST [1046] WARNING: database "template1" has a collation version mismatch
2025-11-06 18:15:30.354 AEST [1046] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2025-11-06 18:15:30.354 AEST [1046] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
2025-11-06 18:15:50.080 AEST [1047] WARNING: database "jfstat" has a collation version mismatch
2025-11-06 18:15:50.080 AEST [1047] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2025-11-06 18:15:50.080 AEST [1047] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE jfstat REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
2025-11-06 18:16:10.110 AEST [1048] WARNING: database "postgres" has a collation version mismatch
2025-11-06 18:16:10.110 AEST [1048] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2025-11-06 18:16:10.110 AEST [1048] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
2025-11-06 18:16:30.370 AEST [1049] WARNING: database "template1" has a collation version mismatch
2025-11-06 18:16:30.370 AEST [1049] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2025-11-06 18:16:30.370 AEST [1049] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE template1 REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
2025-11-06 18:16:50.096 AEST [1050] WARNING: database "jfstat" has a collation version mismatch
2025-11-06 18:16:50.096 AEST [1050] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2025-11-06 18:16:50.096 AEST [1050] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE jfstat REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.
2025-11-06 18:17:10.128 AEST [1051] WARNING: database "postgres" has a collation version mismatch
2025-11-06 18:17:10.128 AEST [1051] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2025-11-06 18:17:10.128 AEST [1051] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE postgres REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.

[CyferShepard]

Hey @vw-kombi , what version of postgres are you running?

[vw-kombi]

I’m pretty sure it’s 16. Not at home currently to check tho.

[vw-kombi]

Correction. It’s 15

[CyferShepard]

I just did a quick search to confirm, this seems to be a postgres issue and not directly related to Jellystat since the error is referencing system tables as well. Here's a quick link to something I found that may help. https://forum.greenbone.net/t/postgres-issue-mismatch/19229

[vw-kombi]

Thanks for that. I’m not real good on the database side. Will figure it out.

[vw-kombi]

I have no idea how to even get into postgres on this docker container to run the commands.......

[vw-kombi]

psql -U postgres I found out.

[vw-kombi]

So summary -

psql -U postgres
reindex database postgres;
alter database postgres REFRESH COLLATION VERSION;

That fixed the postgres one - as it said

NOTICE: changing version from 2.36 to 2.41
ALTER DATABASE

But when I try to reindex database jfstat or template1, it throws -
ERROR: can only reindex the currently open database

But I was able to do these commands -

postgres=# alter database jfstat REFRESH COLLATION VERSION;
NOTICE: changing version from 2.36 to 2.41
ALTER DATABASE

postgres=# alter database template1 REFRESH COLLATION VERSION;
NOTICE: changing version from 2.36 to 2.41
ALTER DATABASE

The logs file now seems to be happy and not spamming any more.

These may help any other postgres newbies like me - who installed this and it just worked.

I now feel more confident on doing the upgarde for my teslamate, which has its own postgres database - I would not want to lose all the tesla history - whereas jellystat I am ok to restart anytime.