It has a similar concept if you need MVCC (with InnoDB). It also has a concept of transaction IDs. And also need to clean them up (purge). They will both have t

It has a similar concept if you need MVCC (with InnoDB). It also has a concept of transaction IDs. And also need to clean them up (purge). They will both have table bloat if not done. Since details matter, there's a post that explains it far better than I could: https://www.enterprisedb.com/blog/mysql-vs-postgresql-part-2-vacuum-vs-purge https://www.enterprisedb.com/blog/mysql-vs-postgresql-part-2...