Hey there! We've found the following might help you get unblocked faster:

• 🧵 Railway Postgres error
• 🧵 Increase Postgres Container Size
• 🧵 Increasing Postgresql memory limit?

If you find the answer from one of these, please let us know by solving the thread!

Hello,

It appears as though you have a custom start command enabled for the postgres container. Please remove that and things should be all good!

Sorry, but I don't know where it is. If it's not too much trouble, could you tell me?

1. Click on the postgres service
2. Go to settings
3. Scroll down to the Deploy block
4. In the Custom Start Command part, if you have a custom command set, click on the command, delete the command, and press the check mark
5. Redeploy the postgres service

i do what ypu say, bu dont work

Do you get a different error or is it the same?

same(

Postgres crashes on startup with

PANIC: could not find free replication state, increase max_replication_slots

Please help recover or fix the database. I cannot change max_replication_slots from the UI.

Hi, to increase that I would recommend downloading the Railway CLI (https://docs.railway.com/guides/cli#%5F%5Fnext) and then SSHing into your service and manually changing the PostgreSQL conf. The flow will look like this:

1. SSH into your service
2. Install text editor by using apt update -y && apt install nano -y

3. Edit the PostgreSQL configuration nano /var/lib/postgresql/data/pgdata/postgresql.conf

4. Search for the max_replication_slots configuration and increase it

5. Save and re-deploy your service

If you aren't able to SSH into your service because it crashes too early, change the startup command to be sleep 1000000000; and remove it after the re-deploy so that it starts normally.