This. I took a lot of inspiration doing this debugging session from my experience as a MySQL DBA. pg_catalog (PG) and information_schema (MySQL) are very simila

This. I took a lot of inspiration doing this debugging session from my experience as a MySQL DBA. pg_catalog (PG) and information_schema (MySQL) are very similar indeed, and I remember finding out index sizes was even way easier in MySQL, the path would have been pretty much the same. Can repeat: Don't switch your database "just because", as Postgres isn't all a happy place. Replication is way harder to set up, it often needs more maintenance, performance is often slightly worse and the tooling is simply better and more mature for MySQL still. MySQL is a formidable SQL-flavored key-value store that scales like hell. Switch when you have a need for CTEs, partial indices, window functions, transactional DDL, CONCURRENT index building or other advanced features.