You'll want to run the VACUUM command on postgres to reclaim the space

Thanks, Jake! I didn't know that. However, when doing so, I get this error: "could not resize shared memory segment "/PostgreSQL.2527481070" to 66454816 bytes: No space left on device"

I understand that this has something to do with shared memory, but this is currently above my pay grade. Can you point me in the right direction for what to look into?

You will need to increase the size of the volume in this case so you can reclaim the space.

Keep in mind, you won’t be charged if you increase the disk size as you are only billed for the disk you use.

Thank you, Angelo. But isn't it a little weird if I have to increase the volume to vacuum a 50GB disk that only uses 5GB?

(I don't know anything about this, so genuine question, trying to understand this better.)

I don't know why Jake changed the status. But I would still appreciate a reply here to understand this better

You may need to bump RAILWAY_SHM_SIZE_BYTES - postgres on containers can be a bit of a pain sometimes.

Try RAILWAY_SHM_SIZE_BYTES=134217728

I tried setting RAILWAY_SHM_SIZE_BYTES=134217728 and was able to VACUUM. But:

1. Disk space didn't decrease, and

2. memory usage spiked from 1-2 GB to +10 GB even though the server was relatively idle. It decrease back to "normal" when I removed the env. variable again.

Isn't an 8GB spike weird?

I'm sorry but we cannot continue to provide assistance here, given the fact that Postgres database is unmanaged and we cannot provide support for 3rd party software.

Perhaps Postgres-centric forums would be able to answer your PostgreSQL-specific questions.