Postgres crashes after changing from legacy to v2 build mode
raik
PROOP

a year ago

My Postgres (PostGIS) does not come up after changing the build mode from legacy to v2. Other services what do not depend on the DB work.

PostgreSQL Database directory appears to contain a database; Skipping initialization

2025-01-23 06:06:26.878 UTC [1] FATAL:  database files are incompatible with server

2025-01-23 06:06:26.878 UTC [1] DETAIL:  The data directory was initialized by PostgreSQL version 16, which is not compatible with this version 17.2 (Debian 17.2-1.pgdg110+1).

View Deploy details

ⓘ Deployment information is only viewable by project members and Railway employees.

Solved

3 Replies

brody
EMPLOYEE

a year ago

Hello,

You had your database set to deploy the latest version, I've reverted it to 16 and the database is now online.

+11

Status changed to Awaiting User Response Railway • about 1 year ago

brody
EMPLOYEE

a year ago

I should also mention that you (Directus) are connecting to the database via the public network, if you connect to the database via the private network you will save yourself on egress fees.

raik
PROOP

a year ago

Thanks for the quick response and proactive fix from your side. Stellar support!

Switched to the private database url. And seems to work now. Didn't get it to work half a year or so ago as the the application (Directus) needed the DB connection on build/deploy.

+11
heart1

Status changed to Awaiting Railway Response Railway • about 1 year ago

Status changed to Solved parmstar • about 1 year ago

Loading...