Comment 11 for bug 1797816

I should make a few other comments

1) New versions of juju have a patch that should prevent ever getting a 200k transaction queue. (if when adding a transaction the queue would be >1000, we reject the txn as invalid.) That should prevent the txn queue from growing large, which was what blocked us from automatically pruning the table, and keeping the size under control.

2) We are currently looking at plans for how we can change the apply step so that it can note invalid transactions and abort them. That also helps get into this situation in the first place.

3) I don't think that we will add something to mgopurge explicitly for this use case, as we should mostly be able to avoid it in the future.