a year ago
DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.
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.
7 Replies
a year ago
Hey there! We've found the following might help you get unblocked faster:
- 🧵 PostgreSQL Collation Version Mismatch Error on Railway Template (PG 17) When Initializing Directus
- 🧵 Problem with postgress passoword after increasing volume
- 🧵 Error on Postgres N8N
- 🧵 Postgres redeploy error
If you find the answer from one of these, please let us know by solving the thread!
a year ago
This solution is not working . Please support with other solution
a year 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 • 11 months ago
a year ago
I have the same error after restore a backup
10 months ago
Anyone got this fixed?
yusuf-ishaku
Anyone got this fixed?
10 months ago
No
10 months ago
Can you share some more details? What project is it? What are you trying to deploy?
10 months ago
I've fixed it on my db running these queries (after a backup):
```
ALTER DATABASE your-db-name REFRESH COLLATION VERSION;
REINDEX DATABASE your-db-name
```
I'm not a db admin, my db was almost empty and it wasn't in prod so I didn't care to break it, I'm not sure if this is the right way but it might be an input for you to do your own research and proceed based on your finding (I do not take any responsibility)....in any case remember to do a backup