News for hackers. Stuff that matters.

A comment on Safely Dropping MySQL Tables. Parent comment

Re:Safely Dropping MySQL Tables by robertlagrant on Monday July 25, 2022 @02:40PM (#32228992)
The safest way is to migrate to Postgres and then do what you like with your MySQL instance.

(I just wanted to win the prize for the most HNey comment ever!)

[ Parent | on HN ]
Re:Safely Dropping MySQL Tables by SnowHill9902 on Monday July 25, 2022 @02:53PM (#32229205)
You are missing Rust somewhere.
[ Parent | on HN ]
Re:Safely Dropping MySQL Tables by itake on Monday July 25, 2022 @03:41PM (#32229905)
OP's solution is objectively worse, because it only reports access recency. Just because the table was or wasn't used recently, doesn't mean its safe to drop.

The code change may of landed the day before that disabled accessing that table, but the tool would warn that the table was still in use.

A quarterly cron job may access the table and go undetected if you look purely at the recency.

The rename strategy protects the data and offers easy rollback. This is a false heuristic.

[ Parent | on HN ]