My PostgreSQL 9.2 database has many AFTER DELETE row-level triggers defined, which are used to delete child rows when a parent row is deleted. (There are also many FKs with ON DELETE CASCADE in cases where the child row references the parent row.) This works, but it's very slow when many rows need to be deleted. Is there a way to use statement-level triggers for this or some other way to make deletes more efficient? I cannot figure out how to get the deleted rows in a statement-level trigger function - or any useful information about what just happened, really.My PostgreSQL 9.2 database has many AFTER DELET