Sarah Clements [pointed out](https://github.com/mozilla/treeherder/pull/6840#issuecomment-741192830) we have this error showing up on treeherder-prototype: ```bash Failed to delete performance data chunk: (Exception: (1451, 'Cannot delete or update a parent row: a foreign key constraint fails (`treeherder`.`perf_multicommitdatum`, CONSTRAINT `perf_multicommitdatu_perf_datum_id_c2d7eb14_fk_performan` FOREIGN KEY (`perf_datum_id`) REFERENCES `performance_datum` (`ID`))')) ``` Looking closer on Papertrail, I can see it reproduces identically on all our environments, including production. Most likely, this bug was added during the multicommit ingestion feature (namely FXP-1201). It seems like when we're deleting multicommit data points from `performance_datum` table, the process somehow stumbles upon the `perf_multicommitdatum` table. `perf_multicommitdatum` is a temporary table we added just to be able to revert the feature, in case we found it buggy in the 1st month. Approximately 2 months have passed since. Assuming it is still working ok, we should also consider removing this table.
Bug 1681473 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Sarah Clements [pointed out](https://github.com/mozilla/treeherder/pull/6840#issuecomment-741192830) we have this error showing up on treeherder-prototype: ```bash Failed to delete performance data chunk: (Exception: (1451, 'Cannot delete or update a parent row: a foreign key constraint fails (`treeherder`.`perf_multicommitdatum`, CONSTRAINT `perf_multicommitdatu_perf_datum_id_c2d7eb14_fk_performan` FOREIGN KEY (`perf_datum_id`) REFERENCES `performance_datum` (`ID`))')) ``` Looking closer on Papertrail, I can see it reproduces identically on all our environments, including production. Most likely, this bug was added during the multicommit ingestion feature (namely bug 1654496). It seems like when we're deleting multicommit data points from `performance_datum` table, the process somehow stumbles upon the `perf_multicommitdatum` table. `perf_multicommitdatum` is a temporary table we added just to be able to revert the feature, in case we found it buggy in the 1st month. Approximately 2 months have passed since. Assuming it is still working ok, we should also consider removing this table. **Jira issue:** https://jira.mozilla.com/browse/FXP-1430