I think you're referring to postgres's inability to use more than one core per query, which is true (or mostly true... there are quite a few helper processes that take on some of the work).
For many smaller queries, postgres does great on multi-core, and pgbouncer is a good connection pooler.
For many smaller queries, postgres does great on multi-core, and pgbouncer is a good connection pooler.