I run few commands manually:
- console core:archive --url=
https://example.com/ - console core:run-scheduled-tasks --force (Info)
- console core:purge-old-archive-data all (Info)
After that, the database tables
segment= 12 rows, 16.0 KiB (all marked as “deleted”).archive_invalidations= 0 rows.
The database mysql dump is yet 1,733 MB (furthermore 50 MB more as expected).
The TRUNCATE of the database table archive_invalidations is fine, because it was 20 MiB.
The furthermore storing of “deleted” segments is not so fine. But it is only 16 KiB.
I think the “Save” of a segment is the cause of the increasing of the database, because, in the month (April) between the monthly mysql dumps …
- 2024-04-01 - 1,650 MB
- 2024-05-07 - 1,733 MB (50 MB more as expected)
… the only what was done differently compared to the months before was a “Save” of a segment (and afterwards “deleting”. This Problem: Problem with Segments).
So, the question here is: It is possible or is it so, that a “Save” of a segment increase the database archive_* tables? And when yes, how is it possible to make it undo?