PostgreSQL Versus MySQL - Isn't a Database Just a Database
Talkat Open Source Summit Europe 2023 · on Wednesday, 2023-09-20· at 16:50· Room 0E-2 (Floor 0), Abandoibarra Etorb., 4, 48011 Bilbao, Bizkaia, Spain·
summary
Comparison focuses on internals not marketing: MySQL uses pluggable engines (InnoDB default) with a clustered primary index so InnoDB clustered primary-key index makes range scans and sequential inserts efficient but secondary indexes store the primary key; PostgreSQL stores row versions in a heap with CTIDs and relies on VACUUM must run or DB halts to reclaim space and freeze XIDs. Undo lives in rollback segments in MySQL vs in-table MVCC in Postgres, and Postgres’ 32-bit transaction IDs risk wraparound so long transactions and absent vacuuming cause real outages; Galera/group replication and differing memory models are practical tradeoffs.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:06PostgreSQL origins
- 2:54Databases compared
- 5:02Evolution over time
- 7:15Neutral comparisons
- 9:25Key differences
- 13:07MySQL architecture
- 16:38PostgreSQL storage
- 23:23InnoDB engine
- 27:19Sequential inserts
- 31:12Indexing differences
- 33:17Multiversion concurrency control in both databases
- 38:57Old row versions
- 41:08Vacuum process
- 44:11Materialized views
- 47:01High availability solutions in MySQL
- 47:46Memory management
- 49:12Q&A
related talks
32mTwo opensource RDBMS: mariadb vs postgresql
31m#PostgreSQL to #MySQL: A DBA Perspective
44m10 reason why you should prefer PostgreSQL to
34mDuel Test: PostgreSQL vs MySQL
16mWhy PostgreSQL took the crown from MySQL and what lies ahead
51mHow Postgres is Different (read BETTER than) your database
18mWhy Postgres Is Better Than MySQL for Automated Knob Tuning
16mJosh Berkus at OSCON: Sun, MySQL, PostgreSQL