We apologize for the instability of composr.app and appreciate your patience. We are working on the statistics addon and trying to find an optimal way to store and render data. Unfortunately, we have yet to find a solution that can handle the traffic (and therefore, tens of millions of statistical records) of composr.app. We're working hard on one.
There was an additional problem I also fixed: TABLE_PURPOSE__FLUSHABLE cannot also define (add) TABLE_PURPOSE__FLUSHABLE_AGGRESSIVE because db_export only wants non-aggressive flushing. But with this definition, all flushing flags returned aggressive.
I removed the addition and ensured that any place that should check both flags is doing so separately.
I removed the addition and ensured that any place that should check both flags is doing so separately.