> AfterTriggerEvents: 2642403328 total in 327 blocks; 10176 free (319 > chunks); 2642393152 used
And there's the problem. Evidently you have an AFTER trigger on the table, and the queued events for that trigger are overrunning memory.
That's interesting - I don't know of any triggers on this table, but it does have a lot of foreign key constraints. Would they fall into the same category?
