Hacker News Reader

All features work all the time

That's the key. Even features which you may not need in particular scenario will add their overhead.

You might not need transactions now, but what if you need then later? If the speed difference between postgress and MySQL performance (what is that, 10%? a boundary case ) is going to kill your app, then get a 10% faster server.

In MySQL case: switch from MyISAM to InnoDB or Falcon (ALTER TABLE table ENGINE=Engine, that's it).

What if you don't need transactions in PG?

Let's not forget MySQL has engines like MEMORY, ARCHIVE, BLACKHOLE (not to mention third party engines).

If you don't need transactions in a DB engine (PG, Oracle, MS SQL, etc), then you don't use them.

I was trying to forget about MySQL and it's plethora of engines.

Reply on news.ycombinator.com