Patch merged to remove it from triggers - need to
- regenerate triggers
- reload triggers (frtech-ops)
- get a 'before DB size'
- drop the table
- get an after db size
- update the 'epic' or wherever we are tracking progress on this
Description
Description
Details
Details
| Project | Branch | Lines +/- | Subject | |
|---|---|---|---|---|
| wikimedia/fundraising/crm | master | +0 -48 | Remove triggers from omnimail_job_progress |
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T241083 Epic: fundraising database approaching data partition capacity | |||
| Resolved | Eileenmcnaughton | T243870 Decide what to do about the increasing civi crm db size | |||
| Resolved | Eileenmcnaughton | T244934 Stop logging & drop log_civicrm_omnimail_job_progress |
Event Timeline
Comment Actions
Change 571845 had a related patch set uploaded (by Eileen; owner: Eileen):
[wikimedia/fundraising/crm@master] Remove triggers from omnimail_job_progress
Comment Actions
@Dwisehaupt @Jgreen Can one of you please drop the following triggers on live Civi DB
DELIMITER
DROP TRIGGER IF EXISTS civicrm_omnimail_job_progress_before_insert
DELIMITER ;
DELIMITER
DROP TRIGGER IF EXISTS civicrm_omnimail_job_progress_before_update
DELIMITER ;
DELIMITER
DROP TRIGGER IF EXISTS civicrm_omnimail_job_progress_before_delete
DELIMITER ;
DELIMITER
DROP TRIGGER IF EXISTS civicrm_omnimail_job_progress_after_insert
DELIMITER ;
DELIMITER
DROP TRIGGER IF EXISTS civicrm_omnimail_job_progress_after_update
DELIMITER ;
DELIMITER
DROP TRIGGER IF EXISTS civicrm_omnimail_job_progress_after_delete
DELIMITER ;
Comment Actions
Change 571845 merged by jenkins-bot:
[wikimedia/fundraising/crm@master] Remove triggers from omnimail_job_progress
Comment Actions
These triggers have been dropped. Only the first three were present.
MariaDB [civicrm]> DROP TRIGGER IF EXISTS civicrm_omnimail_job_progress_before_insert; Query OK, 0 rows affected, 1 warning (0.00 sec) MariaDB [civicrm]> DROP TRIGGER IF EXISTS civicrm_omnimail_job_progress_before_update; Query OK, 0 rows affected, 1 warning (0.00 sec) MariaDB [civicrm]> DROP TRIGGER IF EXISTS civicrm_omnimail_job_progress_before_delete; Query OK, 0 rows affected, 1 warning (0.00 sec) MariaDB [civicrm]> DROP TRIGGER IF EXISTS civicrm_omnimail_job_progress_after_insert; Query OK, 0 rows affected (0.01 sec) MariaDB [civicrm]> DROP TRIGGER IF EXISTS civicrm_omnimail_job_progress_after_update; Query OK, 0 rows affected (0.00 sec) MariaDB [civicrm]> DROP TRIGGER IF EXISTS civicrm_omnimail_job_progress_after_delete; Query OK, 0 rows affected (0.01 sec)
Comment Actions
@Dwisehaupt thanks -- so there are no triggers on civicrm_omnimail_job_progress at all now? (should be the case - just double checking)