How to convert from MySQL to PostgreSQL: discuss history of each, current status, when you might wish to convert, what might motivate you to convert, & how to do so. With references.
2. MySQL vs PostgreSQL
• MySQL covered basics
• But a bit flaky in
practice, under load
• Had looked at
PostgreSQL before, but
relooked
• Others have had similar
problems
http://tapoueh.org/blog/2013/08/08-MySQL-to-PostgreSQL
3. • Clay tablets
• For taxes (but you
knew that)
• The map replaces
the territory
The First
Database
6. MySQL History
• Named after Widenius’s daughter ‘My’!
• Version 5.0 with relational integrity, transactions,
& stored procedures (i.e. real) in 2005
• Bought by Sun in 2008
• Eaten by Oracle in 2010
• Forks: MariaDB (by Widenius), Drizzle
7. PostgreSQL
• Ingres
• Postgres a seQUEL to Ingres
• Postgres95 - released on web
• Open source version 1996
• Has caught up with MySQL on speed & reliability, still
ahead on features
• MySQL is open source, PostgreSQL is open project
9. Why
• Features: i.e. PostGIS, FDW, Stored procedure
languages
• Performance
• Reliability
• Plays nice with others
• Others: culture, fear of Larry Ellison, kool-factor, …
16. Summary
• PostgreSQL makes sense for new projects
• For specific features
• As operational core
• Should be familiar with alternatives: relational,
graph, noSQL, and so on.
17. Further information
• http://www.wikivs.com/wiki/MySQL_vs_PostgreSQL
• https://wiki.postgresql.org/wiki/
How_to_make_a_proper_migration_from_MySQL_to
_PostgreSQL
• http://www.enterprisedb.com/solutions/mysql-vs-
postgresql
• http://www.slideshare.net/akmed13/converting-
from-mysql-to-postgresql