Migrating Uber from MySQL to PostgreSQL

Recommendations

Info

Code Changes Implicit Ordering (cont.) SELECT * FROM trips WHERE status = ’completed’; Without an index on status, the query scans the rows in PK order, so the same implicit ordering on id will occur. With an index on status, the query scans the row in order of (status, id), and thus there is still an implicit ordering on id! (This would not be true for a “range” query, however.) Evan Klitzke (Uber, Inc.) Migrating Uber from MySQL to PostgreSQL March 13, 2013 42 / 59
Code Changes Implicit Ordering (cont.) Disclaimer: I am not a Postgres developer, this is based on what I’ve read online. Postgres does not implicitly cluster indexes on the primary key. Postgres indexes point to the on-disk location/offset of the row tuple, not the row id. Evan Klitzke (Uber, Inc.) Migrating Uber from MySQL to PostgreSQL March 13, 2013 43 / 59
Page 1 and 2: Migrating Uber from MySQL to Postgr
Page 3 and 4: Background Background Uber is a mob
Page 5 and 6: The Objective Background The object
Page 7 and 8: Obstacles cont. Background Addition
Page 9 and 10: Plan of Attack Background To do a m
Page 11 and 12: Background “Replication” Plan,
Page 13 and 14: Background Serialization Problem Th
Page 15 and 16: Conversion Background OK, how much
Page 17 and 18: Conversion Background It turns out
Page 19 and 20: Background MySQLisms (quoting) Quot
Page 21 and 22: Attempt 1 Background My first attem
Page 23 and 24: XML Attempt Background Next I disco
Page 25 and 26: XML Attempt Background New plan of
Page 27 and 28: XML Attempt Background Initial test
Page 29 and 30: XML Attempt Background It turns out
Page 31 and 32: xml2pgcopy Background The final imp
Page 33 and 34: Code Changes Code Changes The other
Page 35 and 36: Boolean Errors Code Changes As note
Page 37 and 38: Timezone Issues Code Changes Produc
Page 39 and 40: ENUMs Code Changes In MySQL, ENUMs
Page 41: Code Changes Implicit Ordering (con
Page 45 and 46: Code Changes Implicit Ordering (con
Page 47 and 48: Code Changes GROUP BY (cont.) MySQL
Page 49 and 50: Case Sensitivity Code Changes Case
Page 51 and 52: Code Changes SQLAlchemy autoflush A
Page 53 and 54: The Actual Migration Production Set
Page 55 and 56: First Attempt The Actual Migration
Page 57 and 58: Interim The Actual Migration In ret
Page 59: The Actual Migration xml2pgcopy, re

Migrating Uber from MySQL to PostgreSQL

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?