Haha, exactly, but if you have developers who can drop production tables without the org knowing in advance and reviewing the change, you already have a big pro

Haha, exactly, but if you have developers who can drop production tables without the org knowing in advance and reviewing the change, you already have a big problem. All our db operations like this go through our regular code review process for the db maintainers team, and instead of dropping tables, we just rename them with a prefix "to_be_dropped" as a scream test, then actually drop them a month later or so. Recovery is much simpler for renaming than dropping.