PostgreSQL left out in database brouhaha
Summary: In all the media excitement over the week's two database deals, Oracle buying BEA Systems and Sun buying mySQL there's a name we're forgetting. It's PostgreSQL.
In all the media excitement over the week's two database deals, Oracle buying BEA Systems and Sun buying mySQL there's a name we're forgetting.
It's PostgreSQL.
PostgreSQL keeps on keepin' on, getting bugs fixed, upgrading its security, and integrating those fixes with major Linux distributions.
PostgreSQL sports a BSD license and has always been considered the more "enterprise-ready" of the open source database systems. It scales especially well for online transaction processing (OLTP) environments.
The best known commercial implementation, Ingres, has a checkered history which has returned it to its open source roots.
The folks at PostgreSQL maintain their own blog about the software, and Version 8.3 is just around the corner.
It's good software, with a lot of users. You might think of it as the John Edwards of database programs. But this isn't politics. PostgreSQL is always available for selection.
Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.
Talkback
For those that want to support themselves, and avoid license problems,
The reason PosgreSQL is left out...
I sense a bias in your coverage that may not be intended, but even the "Ingres" hyperlink in your blog leads to an article about PostgreSQL and the Ingres reference in that article is inaccurate. Ingres and PostgreSQL have a shared parentage but there isn't a single line of code in common between the two products. For a more balanced opinion of Ingres, I'd like to invite your readership to view my blog at http://blogs.ingres.com/emmamcgrattan
Warm regards
Emma McGrattan
Ingres Corp
Talk about bias (nt)
Clearly stated
Postgres doesn't care what its hair looks like
Ba-dum! But seriously... I agree that Postgres' more distributed, diverse community makes it harder to "buy" - and I think this is a good thing, especially for very horizontal, infrastructure-level open source.
I would also posit that it makes for a more scalable open source model. When development doesn't bottleneck with one controlling company (with more or less a single agenda), it's more appealing to hackers who want to roll up their sleeves and get involved.
It might make for more challenging project management (heavier emphasis on meritocracy and consensus, as opposed to corporate fiat), but they keep getting it done! I think the leadership of the Postgres team over the 10 years I've been involved with the project is one of the great untold stories of the technology world.
Cheers,
Ned
--
Ned Lilly
President and CEO
xTuple (formerly OpenMFG)
119 West York Street
Norfolk, VA 23510
tel. 757.461.3022 x101
email: ned@xtuple.com
www.xtuple.com
RE: PostgreSQL left out in database brouhaha
I was surprised to see a mention of a blog maintained by Postgres community!!! The link leads you to an individual's blog, not Postgres' blog...
Please check facts before you post. I don't know how accurate is the other info in this post!
I don't get it
Sun N1 Grid Service Provisioning uses PostGreSQL as its database. Perhaps its for the best; who knows what Sun will do with MySQL - they don't often seem to have a clear direction of where they are going (love Linux today, hate it tomorrow).
RE: PostgreSQL left out in database brouhaha
Version 2.1 is around the conrner with the RC1 in the tests (as we are speaking)
Firebird has the news site here http://www.firebirdnews.org/
Also the fundation can be reached by this url (main project page)
http://www.firebirdsql.org/
BSD license has splintered PostGres
http://www.enterprisedb.com/
http://www.greenplum.com/
I feel that the BSD license has caused the lack of momentum behind Postgres. With GPL software, you must publish the source code if you distribute the software. With BSD, you don't have to give away the source code. While this might make it "enterprise-ready", it has also has caused a lack of leadership when compared to MySQL, which uses the GPL license. Any company can take the Postgres code and create a new product that is a proprietary fork of the original project.
Tristan Rhodes
PostgreSql really is great
among the most stable, feature-complete, well-documented, enterprise-ready
applications I've used, commercial or open source, and apparently had been that
way for years before I discovered it.
I really don't understand why the open source development community seems to
prefer the semi-commercial MySql over the much more mature, powerful, and
completely open PostgreSql. The best explanation I have is that it was only ported
to Windows relatively recently; prior to that it was a Unix/Linux product. Not that
that was technically a bad thing; just that it basically missed the wave of
Microsoft's exploding market share over the past 15 years.