Your SlideShare is downloading. ×
Converting from MySQL to PostgreSQL
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Converting from MySQL to PostgreSQL

1,388

Published on

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.

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.

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,388
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
17
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. PostgreSQL John AshmeadMySQL
  • 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
  • 4. Size matters! • Ad hoc tools • SQLite • MySQL • PostgreSQL
  • 5. Popularity http://db-engines.com/en/ranking
  • 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
  • 8. Decision Points • New Project • Organizational changes • Accumulated stress • Feature lust • Strategic planning
  • 9. Why • Features: i.e. PostGIS, FDW, Stored procedure languages • Performance • Reliability • Plays nice with others • Others: culture, fear of Larry Ellison, kool-factor, …
  • 10. MySQL Gotchas • Nulls->default • Case insensitivity • Select 1/0 -> Null • February 31st http://sql-info.de/mysql/gotchas.html
  • 11. Approachs • hack & go • pivot with frameworks • migration assistants • plan & persevere (step at a time) • halfway houses, i.e. with ODBC
  • 12. Hack & go • Schema level • Data • Application level • Configuration level • Tools • Documentation • Culture
  • 13. Pivot with a framework • SQL Alchemy on Python • Ruby on Rails/ ActiveRecord on Ruby • DBI on Perl • Pear DB on PHP
  • 14. Migration Assistants
  • 15. Plan & persevere • EnterpriseDB • Internal task force • Culture: desperate late night appeals for help often answered
  • 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

×