Currently deleting datum data is extremely slow. The main reason for this is that there is a row-based DELETE trigger defined on the solardatum.da_datum table that inserts "stale data" rows for the deleted rows, which then cause the other aggregate rows to be re-calculated. There should be a more efficient way to do this. The most obvious thing to explore is the elimination of the row-based trigger. This could be expanded to eliminate the row-based trigger for INSERT/UPDATE on solardatum.da_datum as well, although there are data integrity trade-offs to consider. As there is an API to insert "stale data" rows, it might be acceptable to trade off a bit of data integrity for performance.