Still down, production impacted. Volume ID: vol_5yyrdxpxdpuhc3qa

Still down. 10+ hours. No response.

We can confirm your Postgres service is in a crash state and your application is unable to connect to it. This is a known issue where the volume resize completes at the storage level but the filesystem is not properly expanded, so Postgres still sees the old disk size. This requires manual intervention from our infrastructure team to extend the filesystem. We're escalating this now to get it resolved as quickly as possible.

thanks for the update!!

Anytime! ..and we're still looking into this

Thank you

Your volume resize to 20 GB didn't fully apply to the underlying disk, which is why Postgres kept seeing the old size and running out of space. We've corrected this on our end and redeployed your Postgres service. You should now have the full 20 GB available.

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

Thank you so much!

Thanks for the fix guys - we're running a big data import that I didnt realize we needed bigger size. Just want to confirm its ok for me to do live resize to 100gb without it crashing again?

Yes, the fix we shipped addresses the filesystem extension issue you experienced, so live resizing going forward should work without any crashes. One thing to note: Pro plan volumes can be self-serve resized up to 50GB. For 100GB, we can increase that limit for you on our end - just confirm and we'll get it bumped up.

yes please resize to 100gb - thanks again!

Hey, actually, we recently made some changes to the flow and you may be able to self-serve this already - could you please try "Live Resize" your volume from the dashboard?

all set thank you!!

Anytime, and happy building 🚅 !!