mismatch postgres version
sogauto
PROOP

3 months ago

Hi,

I have these messages in my logs. I do not know how to get out this issue. Please could you help me ? I am not able to connect to the client neither with pgadmin nor psql :

2025-12-16 07:03:40.473 UTC [91205] WARNING: database "railway" has a collation version mismatch

2025-12-16 07:03:40.473 UTC [91205] DETAIL: The database was created using collation version 2.36, but the operating system provides version 2.41.

2025-12-16 07:03:40.473 UTC [91205] 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.

Solved$10 Bounty

Pinned Solution

sogauto
PROOP

3 months ago

After multiple attempts, I've succeeded indeed with clients and even with command line psql I wasn't able to connect to the database with this error each time :

error: connection to server at “xxxxxx.xxxx.rlwy.net” (xx.xx.xx.xxx), port xxxxxx failed: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.

Then when I was connected, I ran :

ALTER DATABASE railway REFRESH COLLATION VERSION;

REINDEX DATABASE railway;

and everything worked again.

2 Replies

In a database client (eg, Datagrip), run the following SQL query:

ALTER DATABASE railway REFRESH COLLATION VERSION;


0x5b62656e5d

In a database client (eg, Datagrip), run the following SQL query:ALTER DATABASE railway REFRESH COLLATION VERSION;

sogauto
PROOP

3 months ago

After multiple attempts, I've succeeded indeed with clients and even with command line psql I wasn't able to connect to the database with this error each time :

error: connection to server at “xxxxxx.xxxx.rlwy.net” (xx.xx.xx.xxx), port xxxxxx failed: server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.

Then when I was connected, I ran :

ALTER DATABASE railway REFRESH COLLATION VERSION;

REINDEX DATABASE railway;

and everything worked again.


Status changed to Solved noahd 3 months ago


Loading...