Click on the volume mounted to your database, go to its settings, and increase the capacity.

Redeploy the database after.

when you say increase the capacity what do you mean?

"volume size"

in the service i was attempting to restore and that is stuck and i am not able to resize the volume

Did you click on the volume?

Unless you're already at the max volume for your plan, there shouldn't be any restrictions.

Yes I have clicked on the volume as you can see the attached shows 5GB and the logs still shows no space on the device

Is 5 GB the max you can get?

Also, did you redeploy the service?

No I can get more but as you can see the volume seems to have enough space

Can you resize it and see if it changes anything?

I have resize it to 10GB and is the same error

Please what can i do to get the production data back

Please can I have an update on this please

Hello @Railway can I please have an update on this. This is production issue and I have been following on this since last week. I am keen to know if this is the priority support that its promised

The priority support is for platform issues, from what I can see, they fixed your primary issue within that time frame. Since your issue is now not platform related, there is nothing they can do to help you (except maybe some advice if they have time).

It says that the database is ready to accept connections, are you able to connect to it externally using something like data grip?

Part of the logs show “ready to accept connections,” but the database it’s not able to connect in the same Railway. How is that not a platform issue?

You’re also overlooking the section of the logs that shows the container is still starting. If the container is in the process of starting up, how can the application successfully connect to it at that point?

Also, the fact that I can connect to the database externally doesn’t resolve the core problem. My application and the database are both running within Railway. The issue is that the database cannot connect internally within the same Railway environment, which is what actually matters for this setup.

So tell me how to differentiate between platform issue and other issues please

The issue is within postgres (not the platform) - they can't do anything to fix it.

the section of the logs that shows the container is starting

Railway logs arent the most reliable in terms of their order, if its said 'starting container' in a previous log then its probably an issue.

My postgres (re)starts with the exact same logs as what you've shown, so unless its silently errored, I would like to assume that its working. Is there a specific error that you are getting when trying to connect from your applications?

I am not able to connect to the database because its will try and stop and since its not connecting I can't see the tables too. The app is not connecting too though so I had to spin another service to keep it afloat

Yeah but are you getting any specific errors? Like Failed to connect to [address]:5432?