As mentioned in the issue, would partitioning this old data to some archive tables make more sense than outright deletion?

Out of what's there, deleting old sessions data makes the most sense to me.

Yes, partitioning is ok for most usecases. I wanted to provide additional options, how to deal with old data. Especially in some test CI envs, where is no need for audit, deleting old data could prove useful. I've tried to be more verbose about potentially wrong tables with adding --force, but maybe we shouldn't provide this at all?

it looks possible to make the sql too long at the first run. maybe a temp table make more sense?

updated

:thumbsup:

Commit 72044c1c fixes this pull-request