I've started using postgres at work after a decade of mysql
My expectations were that postgres had a better query engine that was able to make more advanced plans
Operationally it sounded easier to shard mysql, I thought they were the main trade offs
In reality I have been puzzled at the query planner in postgres, rewriting queries to be equivalent (to me at least) causes wildly different plans
Coaxing the engine to use an index is much harder, if not impossible in postgres so far
JSON support seems better but overall that encourages their use which has pros and cons but can definitely hinder schema reading
So far it's not much greener for me on the otherside of the fence, going to continue to evaluate datomic and miss sequel pro, table plus is ok but weird in places
My expectations were that postgres had a better query engine that was able to make more advanced plans
Operationally it sounded easier to shard mysql, I thought they were the main trade offs
In reality I have been puzzled at the query planner in postgres, rewriting queries to be equivalent (to me at least) causes wildly different plans
Coaxing the engine to use an index is much harder, if not impossible in postgres so far
JSON support seems better but overall that encourages their use which has pros and cons but can definitely hinder schema reading
So far it's not much greener for me on the otherside of the fence, going to continue to evaluate datomic and miss sequel pro, table plus is ok but weird in places