Postgres collation version mismatch #7130

Activity

1. cf-mp

   added

   bugSomething isn't workingSomething isn't working

   on Sep 18, 2026
2. Floppy commented on Sep 18, 2026

   

   Floppy

   on Sep 18, 2026

   Collaborator

   More actions

   This often happens when you upgrade the postgres version; has that changed recently?
3. cf-mp commented on Sep 18, 2026

   

   cf-mp

   on Sep 18, 2026

   Last edited by cf-mp

   Author

   More actions

   I do not run an external Postgres server, only what is bundled in as of the compose file.

     postgres-server:
       image: postgres:15
       volumes:
         - /home/manyfold/postgresql:/var/lib/postgresql/data
       environment:
         POSTGRES_USER: manyfold
         POSTGRES_PASSWORD: removed
       restart: unless-stopped
       networks:
         - manyfold
   

   Looks like the current version it is running is 15.19-1.pgdg13+2

   Thanks!
4. cf-mp commented on Sep 21, 2026

   

   cf-mp

   on Sep 21, 2026

   Author

   More actions

   I ended up manually reindexing each of the DBs and it seems to be good now. What should be the best way going forward to manage this? Currently the recommended docker compose file has it pinned to postgres:15 which has about a year of support left. Wondering if you have plans to move to a newer version at some point and if so, is there a way to automatically force a reindex when manyfold sees Postgres has updated to a newer version? Thanks

   for db in manyfold postgres template1; do
     docker exec -it manyfold-postgres-server-1 psql -U manyfold -d $db -c "REINDEX DATABASE $db;"
     docker exec -it manyfold-postgres-server-1 psql -U manyfold -d $db -c "ALTER DATABASE $db REFRESH COLLATION VERSION;"
   done
   
5. Floppy commented on Sep 21, 2026

   

   Floppy

   on Sep 21, 2026

   Collaborator

   More actions

   The postgres version in the docker compose example is just that, an example - Manyfold doesn't manage the postgres install and can't update it. But, there's probably a few things I should do to improve the situation, because a few people will be in the same boat:

   1. Update the example compose file to a newer postgres version
   2. Write some instructions for upgrading the database
   3. Add a CLI or startup job to run that reindex/refresh command

   The same instructions will be needed for MySQL/MariaDB as well.

   Glad you got yours sorted, I'll use what you've put here to improve the documentation.