Exceeding Sotrage Limits?

[Carlos-err406]

Hello Supabase Team.

First of all i would like to say I love what you have accomplished with this product.

For a couple of weeks now I've been getting a warning that my organization is exceding storage usage limits (see attachments)

But i make sure to periodically delete the files from the storage. On Friday, December 6 I even deleted most of the storage objects, from 401 objects to 170, down to 0.04GB (summing up the size from the storage.objects table of the project that had the most objects by far) But that was not reflected on the Storage Usage Chart (see attachment)

Of course i deleted from storage.objects in the sql editor (deleted all objects older than 2 weeks). And made sure they were deleted from the bucket.

So my main concern here is why i keep getting this warning despite i deleted over a half the items of my storage.

Greetings, Carlos Daniel Vilaseca

[GaryAustin1]

You cannot delete files by deleting the storage.objects table rows. You have to use UI or strorage API calls. Any files you deleted using SQL on storage.objects are now orphaned in S3. I personally don’t know of a way to delete them now.

[Carlos-err406]

is there a way to backup the current bucket so i can delete de proyect and create it again?

[GaryAustin1]

This is the only method I’ve seen. https://supabase.com/docs/guides/platform/migrating-within-supabase#migrate-storage-objects

[Carlos-err406]

i tried a similar approach, it worked fine, managed to backup locally all the data and storage objects

i just hope that deleting the supabase project also deletes the orphan objects of the S3

[GaryAustin1]

If you create a new instance it will have its own S3 partition.