Comment by mwexler

I was surprised to see this:

> If joins are necessary, we learned to consider breaking down the query and move complex join logic to the application layer instead.

We often try to leverage the power of the DB to optimize joins on our behalf to avoid having to create them. At a certain point, I guess you wind up having to pull this back to your layer to optimize "the one job" of the database.

I jest, but only slightly. We don't just want to persist data, but link it for different purposes, the "relational" part of RDBMS. Good to know there's still room to grow here, for PostgreSQL and the DB industry.