It's been a long wait but replication is now finally as easy as it gets. And, by design, it can not silently lose or corrupt data. Unlike a certain other popular RDBMS.
For my part, I'm stoked about 9.0. It can't get here soon enough.
Well, to clarify, a lot of popular pre-packaged software is out there in PHP. And PHP never had a good db abstraction layer + the entire style of the PHP language lent itself to the direct use of queries in the code, and the direct usage of the MySQL connectors.
When users want a forum, a wiki, a helpdesk, a blog, etc. and it's in PHP, chances are it doesn't have a PostgreSQL backend. And if you have to have MySQL, and MySQL works for everything (for some definition of the word "works") while PostgreSQL doesn't... there's your answer.
The real reason is: PostgreSQL doesn't have any must-have apps that only run PGSQL (which is a good thing), and MySQL does (which is a bad thing) so MySQL wins.
Most widely used blog engine (CMS?) in the world - only MySQL. http://codex.wordpress.org/Using_Alternative_Databases
Drupal is probably one of the few PHP CMS that work with PG - http://geek.joshwaihi.com/content/drupal-7-postgresql-suppor...
I've done the 'apt-get install postgresql' routine a few times, and started to play with it, but due to it being different enough, and without any compelling motivation, I've never been able to learn it beyond scratching the surface.
That said, I'm a developer, and not a DB admin, so the limitation is almost certainly mine.
Its success was due to illusion of simplicity and easiness + massive community of believers ^_^
PostreSQL sites is rather shy comparing to them.
I agree. PG is becoming better and better with every release. It can compete with Oracle in some applications. Personally I hope they implement Row Level Security some time. It's my favorite feature in Oracle and I hope they will implement something similar soon.
Please do your homework before spreading FUD. PostgreSQL is used at large scale every day, e.g. at Skype: http://highscalability.com/skype-plans-postgresql-scale-1-bi...
More examples can be found here: http://www.postgresql.org/about/users
Setting "synchronous_commit = off" nets you 99.9% of the performance improvement without the possibility of corrupting your entire database.
MySQL's working on this (http://mysql.com/oem/), but I've read that PostgreSQL is way too tied to their multi-process network architecture for this to be feasible. But I'd love to be shown to wrong on that.
The important part is that you'd be able to easily statically link to it and handle permissions on a by-file basis, instead of PostgreSQL's current permission model. For all intents and purposes it'd be a larger SQLite replacement then.
I don't know how they manage it, but every release adds features and becomes more stable. Pretty awesome job.
A very high quality product, indeed.
Thank you, everyone behind the development of PostgreSQL. I wouldn't be in my life where I am now if it wasn't for the work you are constantly putting into this wonderful project.
And when one thinks "now. this is it. it can't get any better now", you come out with another high-quality release.
Thank you ever so much.
