We can confirm your volume resize hasn't propagated to the filesystem, which is why Postgres still sees the old 20GB limit and is crash-looping on WAL writes. We've flagged this for our infrastructure team to manually extend the filesystem.

Hi! We've expanded the filesystem on your Postgres volume to match the full 20 GB allocation and redeployed the service. The resize wasn't fully applied on our end, which is why Postgres kept crash-looping. It should come back up shortly with the full disk space available. We've also shipped a fix to prevent this from happening on future volume resizes.

To be clear, I resized the volume to 100GB but my Postgres filesystem is still only showing 20GB disk space available. Did you resize Postgres to 20GB or 100GB?

My volume size is still currently showing it's set to 100GB so I don't want to try changing that. I just need my Postgres filesystem to match it at 100GB.

Apologies for the confusion. It looks like the filesystem was only extended to 20GB rather than the 100GB you requested. We're flagging this again for our infrastructure team to extend the filesystem to the full 100GB to match your volume setting. Please don't change the volume size in the meantime.

Thanks. Please let me know when done, and also is this something that will continue to happen? Will I need to reach out to manually request the resizing each time I attempt a resize from the Railway admin?

Your volume resize to 100 GB didn't fully apply, which is why Postgres was still seeing the old disk size. We've corrected this on our end and redeployed your Postgres service. You should now have the full 100 GB available.

We've shipped a fix to prevent this from happening on future volume resizes, so you won't need to reach out for manual intervention again.