Your Postgres service is currently in a crashed state. When a volume hits 100% capacity, a live resize triggers an offline resize with data integrity checks that restarts the service, but if Postgres was already crash-looping due to the full disk, it may not recover automatically. Try restarting the service from the deployment's three-dot menu to allow Postgres to start fresh with the newly available space. If the "No space left on device" error persists after restart, the volume may still not be large enough since accumulated WAL files can consume significant space, and you would need to resize the volume further.

Hey! The volume resize didn't fully apply to your Postgres database, so it was still operating with the old, smaller disk size. We've corrected this on our end and redeployed your Postgres service. You should now have ~5 GB of available disk space.

We've also shipped a fix to prevent this from happening on future volume resizes.

Thanks, Brody! Yesterday was a CHAOTIC day hence the reason why I did not answer.

But the issue was resolved and everything is back to its normality. Thanks a lot!