Bug: log_civicrm_group table grows insanely quickly
(Agileware ref CIVICRM-1001)
Best demonstrated by example:
select count(id) `entries`, count(distinct id) `ids`, min(log_date) `since`, now() `now` from log_civicrm_group;
|31813||223||2018-10-16 14:14:51||2018-10-17 11:03:18|
This is for a < 22hr period after I cleared this table to try and solve a data migration issue; before, this particular log table had grown to nearly 7 gigabytes (for the same 223 distinct group ids).
What appears to be happening is that every time the group_rebuild job is called, the cache_date is being NULLed and filled back in, creating two additional pointless log entries. Per group id, I counted up to 250 log entries where only these fields had changed.
I think it should be possible to fix this by one of:
- Disabling logging the the group_rebuild API call runs; or
- excluding changes to just the cache_date and refresh_date fields from the civicrm_group triggers