But no database that ensures ACID can avoid that one.

If that's the problem, we should say "Postgres isn't slow, you're just on ACID".

But then again, only the transaction log has to be physically on the drive to guarantee durability, and modern drives are very good at sequential writes. Writing tables/indexes can be delayed (to a "checkpoint", as it is known in most database systems).