9 days ago
Database storage suddenly spiked to full storage. It's at the maximum it can be upgraded to on the Pro plan, hence unable to increase further. So currently unable to even connect to the DB to do clean up and vacuuming.
I've scheduled a meeting already to upgrade the storage further. Posting here hoping there's a faster way to resolve the issues.
7 Replies
9 days 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!
9 days ago
Your database volume has been increased to 300GB and it’s now back online and accessible. You should be able to connect and perform any necessary cleanup or maintenance. If you run into any further issues, let us know.
Status changed to Awaiting User Response Railway • 9 days ago
Status changed to Solved brody • 9 days ago
9 days ago
Thanks for the quick assist. However, it seems like I'm still unable to connect to my postgres database. The errors in the deploy logs are as follows:
```
2025-11-27 04:34:39.456 UTC [161] LOG: invalid length of startup packet
2025-11-27 04:34:45.750 UTC [164] LOG: invalid length of startup packet
2025-11-27 04:34:48.828 UTC [165] LOG: invalid length of startup packet
2025-11-27 04:34:51.947 UTC [167] FATAL: unsupported frontend protocol 65107.19778: server supports 3.0 to 3.0
2025-11-27 04:34:52.022 UTC [168] FATAL: unsupported frontend protocol 65363.19778: server supports 3.0 to 3.0
```
The database connection still cannot be established it seems.
Attachments
Status changed to Awaiting Railway Response Railway • 9 days ago
Status changed to Solved brody • 9 days ago
9 days ago
The database has been cleaned. You may reduce the size of the DB back to 250GB now.
Status changed to Awaiting Railway Response Railway • 9 days ago
9 days ago
Thanks a bunch!
Status changed to Awaiting User Response Railway • 9 days ago
Status changed to Solved brody • 9 days ago
