PostgreSQL scales

Via zillablog, I was notified of FeedLounge switching to PostgreSQL

FeedLounge is just another in a serious of webbased services switching their RDBMS away from MySQL.

For one thing, it’s the features that’s driving this. Postgres just has more features and sometimes, you need to have them. Triggers? Views? Until very recently, those features were not available with MySQL.

And when they switch, they notice another thing: PostgreSQL scales very well.

While everyone says that MySQL is optimized for speed and that there’s no database system as fast as MySQL, this is only true for small setups.

In small setups MySQL scores with its ease of use and administration. But as soon as you want more (more features, more users accessing), you will run into MySQL’s limitations and – even more important: MySQL will slow down, it will use lots of RAM and disk space and it even will begin to corrupt it’s tables (a thing a RDBMS should never ever do – not even in case of broken hardware though that’s unavoidable).

PostgreSQL does not have these flaws. It may be a little bit slower under low load, but it speed and reliability scales with its users.

PostgreSQL scales.