Why Oracle Can't Easily Kill PostgreSQL
ruphus13 writes "Claiming that 'PostgreSQL is a FOSS alternative to MySQL and hence Oracle should be allowed to pursue MySQL' is a specious argument, according to Monty Widenius. He fears that Oracle, or someone else, can easily squash PostgreSQL by just 'buying out' the top 20 developers. The Postgre community has fired back, calling that claim ridiculous. According to the article, 'PostgreSQL as a project is pretty healthy, and shows how vulnerable projects like MySQL are to the winds of change. PostgreSQL could die tomorrow, if a huge group of its contributors dropped out for one reason or another and the remainder of the community didn't take up the slack. But that's exceedingly unlikely. The existing model for PostgreSQL development ensures that no single entity can control it, it can't be purchased, and if someone decides to fork the project, the odds are that the remaining community would be strong enough to continue without a serious glitch.'"
I would like to have a list of serious companies using PostgreSQL for serious stuff...and what stuff it is PostgreSQL is doing. In my world, all you hear is "...MySQL...MySQL...", even in cases where the back-end is being handled by PostgreSQL.
Our three major DBs have about 13.4 million records combined, with enormous amounts of data about clients. PostgreSQL has never failed us. I work in the insurance business.
You forgot SQLite. It's small and good enough for most of what MySQL gets used for: simple web forms, stat counters etc.
His argument is "I was bought, therefore anybody else can be bought".
If Oracle is willing to buy 20 developers at $1 billion each, then he may be right.
Richard Stallman has clarified that he believes the GPL is necessary and sufficient protection for MySQL, in direct contradiction to Widenius' call that the license should be changed and copyrights rest in some entity other than Oracle.
Eben Moglen and the Software Freedom Law Center defend the GPL even more strongly:
you had me at #!
It's not a multiuser database.
A web site is a classic multiuser scenario for an RDBMS; you have to have concurrency issues completely nailed down (ideally with row level locking and ACID).
It's also MySQL's sweet spot.
you had me at #!
What? The open source replication alternatives are good enough
You have:
* PGCluster
* Slony-I
* DBBalancer
* pgpool
* PostgreSQL table comparator
* SkyTools
* Sequoia
* Bucardo
* Mammoth Replicator
* Cybercluster
* GridSQL (shared-nothing)
All are open source and some even offer additional commercial support.