Home > slashdot > Why Oracle Can’t Easily Kill PostgreSQL

Why Oracle Can’t Easily Kill PostgreSQL

January 9th, 2010 01:20 admin Leave a comment Go to comments

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.’”

Source: Why Oracle Can’t Easily Kill PostgreSQL

Related Articles:

  1. PostgreSQL 9.0 Released
  2. Oracle Releases MySQL 5.5
  3. What Is New In PostgreSQL 9.0
  4. Widenius Warns Against MySQL Falling Into Oracle’s Hands
  5. Oracle May ‘Fork Itself’ With MySQL Moves
blog comments powered by Disqus