[feature] Remove tombstones

[mirabilos]

[feature] Remove tombstones

[tsmethurst]

Thanks!

No problem!

That’s #1919 then AFAICT.

Yep :)

[tsmethurst]

I think you can safely delete your tombstones in this case, manually, if that 34MB would help. In future we could indeed clean them up on a schedule to save a bit of space. As you point out, they're mostly important for only a limited period of time anyway.

The media_attachments table is also huge. Does the media cleanup not remove rows in it?

No. It just uncaches attachments from storage and updates the media attachment entries. The statuses themselves keep references to those attachment IDs.

When we implement status cleanup, then media attachments will also be deleted when statuses are deleted.

[mirabilos]

tobi dixit:

I think you can safely delete your tombstones in this case, manually, if that 34MB would help.

Ah okay, thanks. It would have helped on the old VM; on the new one, I think the entire 3+ GB PostgreSQL fits into RAM via buffer cache… at least for now where GtS is the only thing on it, I have yet to migrate other things but the I/O-heavy one stays on the old VM, so I should not have as much pressure as before.

In future we could indeed clean them up on a schedule to save a bit of space. As you point out, they're mostly important for only a limited period of time anyway.

Thanks. I was just collecting what cleanup ideas I had.

> The media_attachments table is also huge. Does the media cleanup not > remove rows in it? No. It just uncaches attachments from storage and updates the media attachment entries. The statuses themselves keep references to those attachment IDs.

OK. Makes sense.

When we implement status cleanup, then media attachments will also be deleted when statuses are deleted.

Thanks! That’s #1919 then AFAICT. bye, //mirabilos