Ask yourself why you are paying so much in licensing costs and annual maintenance when you could use PostgreSQL.
- it’s free
- you get community support
- upgrades are free as well
In terms of standard SQL support, PostgreSQL is very good indeed. If a feature is in the SQL92 standard, you can be pretty sure that PostgreSQL is going to support it correctly.
I advise developers to stay away from extensions to the SQL standard in any case.
The ability to write functions and stored procedures is somewhat limited in PostgreSQL.
The advantages of PostgreSQL are cost and the ability to look at the source code to understand what’s going on. Very few developers will ever make changes to the source or, even better, submit fixes. I do believe the ability to examine the code in order to understand why something doesn’t behave as you expect is a great benefit.
In my opinion, PostgreSQL is enterprise ready. For many uses, PostgreSQL is just as suitable as Microsoft SQL Server or Oracle, but with a big cost advantage. The features that you need 95% of the time are there and work as expected. The underlying engine is very stable and copes well with a good range of data volumes. It also runs on your choice of hardware and operating system, not just whatever some big vendor might insist you buy to run your database .
Of course, it’s not the solution to all database needs, any more than any other vendor’s product would be. For a large, multi-terabyte data warehouse you still need a specialized database product with some advanced features, specifically for handling those kinds of data volumes.
It’s difficult to see why you would use MySQL and PostgreSQL side-by-side. MySQL has historically traded some functionality for performance. For most purposes, you don’t need to make that trade, and PostgreSQL performance is more than adequate.
http://www.postgresql.org/
install