09:25:50.777 [info] Pruning objects older than 90 days, keeping non public posts, keeping threads intact, pruning orphaned activitiesRunning the forbidden task ;)
pleroma-pruned-db-winning.png
Timeline
Post
Remote status
Context
7pleroma-pruned-db-winning.png
@phnt let me know how big ur db is after. i ran this on my old pleroma db (after getting the sql query out of the debug logs cuz the mix task kept timing out) and it went from 127gb to 127gb
@phnt @pwm
>salon 78gb
>delete from activities where data->>'type' = 'Announce' and split_part(data->>'actor','/',4) = 'relay';
>DELETE 7018354
>salon 78gb
that did NOTHING. here's the screenshot if u dont believe it. its an old dump.
image.png
>salon 78gb
>delete from activities where data->>'type' = 'Announce' and split_part(data->>'actor','/',4) = 'relay';
>DELETE 7018354
>salon 78gb
that did NOTHING. here's the screenshot if u dont believe it. its an old dump.
image.png
Replies
8
@pwm @pernia It is more complicated than that. pg_relation_size is the disk size for one fork of the table (main, init, vsm,...) pg_total_relation_size is all of those together, which is what \l+ in psql uses. To calculate estimated disk size after a delete without VACUUM FULL, you need to get the size of tuples in the table and do the same for indexes.