How Postgres is Misused and Abused in the Wild

Maybe the functionality that the user wants doesn't exist. Maybe they've implemented a particular architecture because they're working around constraints in their own infrastructure that they can't actually do anything about. Maybe the most appropriate architecture for their use case isn't well documented or explained. Maybe the user doesn't understand something because there aren't enough training resources, or we've not made it clear to the users where they can find the training resources that they needed. … Lots of people are setting really, really high values of max_connections. Although it's a lot less of an issue than it used to be, it's still causing problems. I'm hypothesising, but I suspect that it's an education issue, especially with people coming from other database management systems; that we still need to explain to users how Postgres works, what the implications are if they set max_connections too high, and if they have too many concurrent connections.