Comment 2 for bug 1403080

A couple of workarounds:

-- The nuclear option:
TRUNCATE TABLE maasserver_event;

-- A slightly nicer option:
ALTER TABLE maasserver_event DISABLE TRIGGER maasserver_event_event_delete_notify;
DELETE FROM maasserver_event WHERE id < 6000000;
ALTER TABLE maasserver_event ENABLE TRIGGER maasserver_event_event_delete_notify;

I'm not sure we actually want this trigger to be there; it's
automatically created to keep the UI up to date. For the event log I
think we could dispense with tracking DELETE.