3 ms·
MySQL can handle many more connections per instance than postgres. Often when you have a high-transaction database in prod with postgres, you need something lik
by nknealk 5y ago
MySQL can handle many more connections per instance than postgres. Often when you have a high-transaction database in prod with postgres, you need something like pgbouncer to handle connection pooling or you'll have a bad time.
I agree though that postgres has some fantastic features.
edit: I think they may have addressed some of this in a recent version? I'm basing my knowledge on postgres 12
- mattashii 5y agoConnection scaling in postgres works better with the more recent versions. Still, you might indeed want to implement a connection pool for your PG instance if you have large swathes of mostly idle connections due to the single-backend-per-connection constraint of postgresql.