News:
I run few commands manually:
- console core:archive --url=
https://example.com/ - console core:run-scheduled-tasks --force
- console core:purge-old-archive-data all
After that, the database tables
segment= 12 rows, 16.0 KiB (all “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.
Are you sure the segmented report is the thing that makes your DB too high?
I think so, because, in the month (april) between the monthly mysql dumps …
- 2024-04-01 - 1,650 MB
- 2024-04-07 - 1,733 MB
… 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, let us close this Topic and let us continue here: