Switching Teams: Moving an Application from MySQL to PostgreSQL

on YouTube ↗38m

" summary

Migration converts a 2005 MySQL-backed Catme app to PostgreSQL using mysqldump (ANSI mode), sed/perl/C scripts and iconv to repair mixed encodings; enums, AUTO_INCREMENT→sequences, indexes and timestamp behavior are rewritten and many MySQL-specific queries are refactored to standard SQL. Tests run about threefold faster immediately; many tests fail until SQL idioms and date logic are fixed. Production data reveals TIS-620 and CP949 rows that require per-country extraction and recoding with iconv + C fixer; no PostgreSQL extensions are required for full functionality.

AI-written summary · about

" chapters (10)

1. 0:00Introduction
2. 1:15Why switching databases is not straightforward
3. 4:02Choosing PostgreSQL over MySQL
4. 9:20Schema migration challenges
5. 12:15Schema and data type differences
6. 16:38Performance improvements
7. 17:46Code changes for PostgreSQL
8. 22:00Testing production data
9. 27:24Fixing non-UTF8 data
10. 31:08Q&A

" related talks

• 57mCase Study, Converting the CATME application from MySQL to PostgresJulier Baumler · PostgresOpen 2013
• 59mLarge Scale MySQL Migration to PostgreSQLDimitri Fontaine · Postgres Open 2012
• 45mSQL Server to PostgreSQL: Migration Challenges & SolutionsSameer Kumar, Roneel Rohitesh Kumar · FOSSASIA PGDay 2025
• 27mMigrating from MSSQL to PostgreSQLRobert Bernier · Percona Tech Days 2020
• 48mMigrating to PostgreSQL: Strategies, Sovereignty, and SuccessRaphael Salguero · PostgreSQL Conference Europe 2025
• 06mMigration Consideration Oracle to PostgreSQLNeeta Goel · PGConf India 2025
• 29mTales from the Field - Oracle to PostgreSQL migrationsAdithya Kumaranchath · POSETTE: An Event for Postgres 2024
• 43mMigrating Away from MySQL for an awesome full text searchPeter Bengstsson · PostgresOpen 2014