5 months ago
I set a usage limit that was hit yesterday ($60). I upped the limit and redeployed everything (including the DB), but it looks like the collation is wrong from the logs:
2025-09-07 20:38:03.850 UTC [388] WARNING: database "railway" has a collation version mismatch
2025-09-07 20:38:03.850 UTC [388] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
2025-09-07 20:38:03.850 UTC [388] HINT: Rebuild all objects in this database that use the default collation and run ALTER DATABASE railway REFRESH COLLATION VERSION, or build PostgreSQL with the right library version.The DB is unresponsive when I try connect, or do a dump, and I'm unable to re-index.
I'm now worried about my data.
5 Replies
5 months 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!
5 months ago
Database is unresponsive and won't allow any connections. I've tried:
- psql via the public URL (just hangs)
- psql via a hosted instance (just hangs)
- I've tried re-deploying it... same as above
I've upgraded to the Pro plan just to get faster support. Having second thoughts about using Railway in production after this.
5 months ago
Hello!
We're acknowledging your issue and attaching a ticket to this thread.
We don't have an ETA for it, but, our engineering team will take a look and you will be updated as we update the ticket.
Please reply to this thread if you have any questions!
5 months ago
🛠️ The ticket Storage access issue has been marked as triage.
Status changed to Awaiting User Response Railway • 5 months ago
5 months ago
🛠️ The ticket Storage access issue has been marked as todo.
Status changed to Closed ray-chen • 5 months ago