Hacker News Reader

But at least Postgres has much better tools for learning about the query plans it might use. The Postgres output of “EXPLAIN” is much much better than MySQL.

It’s a shame that almost every job I worked at uses MySQL and not Postgres. But that could be because those companies all got their start like a decade or more ago when Postgres was not as well known.

> As a huge Postgres fan working at a shop using MySQL I'll point out the first thing I saw MySQL does that Postgres doesn't:

> Index hints.

Eh, it's an extension. One you shouldn't use, but it's there.

I didn't know this!

> I would still rather work with Postgres AND have to juggle a connection pooler

Is this comment relating to the overhead of idle connections, which has historically necessitated the use of a pooler in front of PG? If so, I believe this is resolved in postgres 14

https://pganalyze.com/blog/postgres-14-performance-monitorin...