have you tried resize your volume?

In that state PostgreSQL won’t let you connect, so you can’t delete data or run queries. There’s really no workaround from inside.

Since you're on the Hobby plan in Railway, I’d first check if you have backups or snapshots available. If you do, the quickest way out is honestly to spin up a new PostgreSQL instance and restore the latest backup. If your backups are frequent (or effectively unlimited in your setup), just restore and move on — that’s usually faster than trying to “fix” the broken instance.

If you don’t have backups, then you’re kind of blocked until you add more disk. That means upgrading your plan, increasing the storage, and restarting the database so it can exit recovery.

Another thing you can try, if Railway allows it in your project, is creating a second instance or replica and recovering data there — but in practice, the cleanest solution is still restore-from-backup.