#PostgreSQL to #MySQL: A DBA Perspective
summary
Yelp runs MySQL 5.6 with statement-based replication and replication trees up to five nodes deep, supporting ~400 engineers and doing ~15 schema changes per week with four DBAs; large updates cause cascading replication lag while Postgres replicas stall on block locks. Postgres offers WAL streaming, transactional DDL and rich index types (GiST, GIN, BRIN) plus functional indexes and create index concurrently for nonblocking builds; MySQL uses InnoDB clustered B‑trees so long primary keys bloat every secondary index.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 4:21Database replication
- 8:25Managing schema changes
- 11:12Analyzing query plans
- 14:36Indexing strategies
- 18:40Community and final thoughts
- 21:13Q&A session
related talks
50mPostgreSQL Versus MySQL - Isn't a Database Just a Database
44m10 reason why you should prefer PostgreSQL to
34mDuel Test: PostgreSQL vs MySQL
52mMySQL replication deep dive, and ideas for PostgreSQL
16mWhy PostgreSQL took the crown from MySQL and what lies ahead
13mBuilding reliable infrastructure with Postgres
51mHow Postgres is Different (read BETTER than) your database
59mLarge Scale MySQL Migration to PostgreSQL