> If you want full data guarantees, with regular hard drives, you'd be looking at less than 200 transactions per second.

That sounds like an anecdote from the time before SSDs.

> "setting this parameter to off does not create any risk of database inconsistency: an operating system or database crash might result in some recent allegedly-committed transactions being lost, but the database state will be just the same as if those transactions had been aborted cleanly. "

If your application is told that the transactions were committed, but your DB actually hasn't, you got a problem, methinks.