Can no longer connect to Postgres after upgrade
Anonymous
PROOP

6 months ago

Since upgrading the Postgres database for our n8n instance, the connection tab on Postgres is spinning and the logs show the below message. Does anyone know how we can connect to the database and update the collation while it is in this state?

2025-09-09 12:17:08.165 UTC [77] WARNING: database "railway" has a collation version mismatch

2025-09-09 12:17:08.165 UTC [77] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.

2025-09-09 12:17:08.165 UTC [77] 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.

3 Replies

Railway
BOT

6 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!


6 months ago

Apologies but this looks like an issue with the application level code. Due to volume, we can only answer platform level issues.

I've made this thread public so that the community might be able to help with you query.


Status changed to Awaiting User Response Railway 6 months ago


6 months ago

The connection tab only works over the Railway public network and you don't have that configured for your Postgres. The ALTER DATABASE message is harmless and your Postgres looks to be working correctly. If you want, you can run the suggested command manually, but it should still be working without that.


Loading...