Skip to content

About this new MySQL Emulation Layer in PostgreSQL 9.0

This blog post of mine about the new MySQL Emulation Layer in PostgreSQL 9.0 was (more of less obvious) an april joke. Most readers have guessed right.

On the other hand the idea, that this joke is based, is very real: during the last conferences and exhibitions which I have attended, a lot visitors asked us (the PostgreSQL booth staff) about the future of MySQL.

Guess what - we don't know! Please ask Larry ;-)

The next question was usually about porting a MySQL database to PostgreSQL. Many companies selling products with MySQL inside are irritated - and frustrated: "Can i still buy a MySQL license in a year or two?" - "And if yes: how many bucks will Oracle request for this?". "Will Oracle still offer support or will they try to convience everyone to use Oracle database?" At this point many companies start to look for some other database - and PostgreSQL is there, happy to help.

I would like to thank David Fetter at this point, he did the proofreading for my post.


One note for me for future april jokes, or other posts: I really must have more webserver and database power available ;-)

During the day everything was ok - and then the americans woke up and my blog was hammered done, access count skyrocked during one hour, server load exploded. Someone added the blog post on reddit.com, this was the cause for a good part of yesterdays traffic.

This blog is running by default inside a virtual machine, both webserver and database. During the evening (european time) I decided to move the database off to another host. This helped to bring the blog up again and serve all requests without further trouble. Yesterday I have seen so many requests as usually in a full month. Very nice.

  • Twitter
  • Bookmark About this new MySQL Emulation Layer in PostgreSQL 9.0 at del.icio.us
  • Facebook
  • Google Bookmarks
  • FriendFeed
  • Digg About this new MySQL Emulation Layer in PostgreSQL 9.0
  • Bloglines About this new MySQL Emulation Layer in PostgreSQL 9.0
  • Technorati About this new MySQL Emulation Layer in PostgreSQL 9.0
  • Fark this: About this new MySQL Emulation Layer in PostgreSQL 9.0
  • Bookmark About this new MySQL Emulation Layer in PostgreSQL 9.0 at YahooMyWeb
  • Bookmark About this new MySQL Emulation Layer in PostgreSQL 9.0 at Furl.net
  • Bookmark About this new MySQL Emulation Layer in PostgreSQL 9.0 at reddit.com
  • Bookmark About this new MySQL Emulation Layer in PostgreSQL 9.0 at blinklist.com
  • Bookmark About this new MySQL Emulation Layer in PostgreSQL 9.0 at Spurl.net
  • Bookmark About this new MySQL Emulation Layer in PostgreSQL 9.0 at Simpy.com
  • Bookmark About this new MySQL Emulation Layer in PostgreSQL 9.0 at blogmarks
  • Bookmark About this new MySQL Emulation Layer in PostgreSQL 9.0 with wists
  • wong it!
  • Bookmark using any bookmark manager!
  • Stumble It!
  • Identi.ca

Trackbacks

www.bottledcomputer.com on : PingBack

Show preview
Comments ()

sourcecodebank.com on : PingBack

Show preview
Comments ()

www.fcjoy.com on : PingBack

Show preview
Comments ()

Comments

Display comments as Linear | Threaded

Joshua Kugler on :

Add to this that someone has written a drop-in layer for running Oracle applications on top of PostgreSQL, and your MySQL emulation layer post just might be taken seriously. :) I wonder if there are any projects in the works to write a raft of stored procedures (or an add-in lib) to match all of MySQL's built-in functions so applications can be ported with minimal fuss.
Comments ()

Andreas 'ads' Scherbaum on :

There are fundamental differences between Oracle-PostgreSQL and MySQL-PostgreSQL, I picked some in my posting. As example the || operator, schemata (ok, this one should be easy), storage engines, the GROUP BY issue ect. ect. and so on. Porting from and to Oracle is much easier, because Oracle follows more or less the SQL standard. There are differences, of course, but that's not a big deal. Porting from MySQL (I only heard about one company which ported from PostgreSQL to MySQL) is way more difficult because of all the non-SQL-standard issues. My book contains one chapter just about this issues. For starters, there's the mysql2pgsql project: http://pgfoundry.org/projects/mysql2pgsql/
Comments ()

Robert Treat on :

Actually, there already is a project that rewrites most of the built in mysql functions for postgresql. I'm hoping to spruce it up for 9.0, but what's there is certainly helpful if you into porting projects. http://pgfoundry.org/projects/mysqlcompat/
Comments ()

Andreas 'ads' Scherbaum on :

As the "General Compatibility Notes" state: some differences aren't portable and need manual investigation. On the other hand: it's good to have a start and this project aims to fulfill this expectations. Keep working on this, i just added a note to mention the project in the next release of my book.
Comments ()

sxpert on :

you should probably add a caching layer to the blog engine...
Comments ()

Andreas 'ads' Scherbaum on :

I leave this topic to someone else. Have already filed a good number of bug reports about the PostgreSQL support in s9y ;-)
Comments ()

Add Comment

Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
E-Mail addresses will not be displayed and will only be used for E-Mail notifications.
To leave a comment you must approve it via e-mail, which will be sent to your address after submission.
Form options