19 days ago
Hi Railway team,
I'm seeing collation version mismatch warnings in my logs:
"The database was created using collation version 2.36, but the operating system provides version 2.41."
As I'm not a superuser, I can't run:
ALTER DATABASE railway REFRESH COLLATION VERSION;
Can you please run this command on my behalf or advise the best course of action?
Thanks in advance!
2 Replies
19 days ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
19 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 19 days ago
18 days ago
Hey! Quoting my friend uxuz on this solution:
According to the Postgres docs, you would want to reindex and update the collation version of your Postgres database. This can be done by running REINDEX DATABASE railway; and ALTER DATABASE railway REFRESH COLLATION VERSION;. Make sure to backup your database before executing these queries, in case they fail and somehow corrupt the database. Having a backup also allows you to just deploy a new Postgres database and restore the backup to it, this way you have multiple ways to restore your database as opposed to just the one I mentioned first.
His solution helped another user.
I can't stress enough ensure you have a backup of your database even if it is a "safe" command, one that is confirmed to work, it is always a good idea to have a failsafe.