This. I have years of experience on Sql Server and just recent months on Postgresql, but I found the latter lacks simple and easy troubleshooting tooling. Bad q

This. I have years of experience on Sql Server and just recent months on Postgresql, but I found the latter lacks simple and easy troubleshooting tooling. Bad query plan issues in Sql Server are not really an issue, something like the problem of this post would have take minutes to discover and fix using query store, that you can turn on and off when needed (I usually left it on, space is capped). Also if there were multiple plans computed and cached you could have forced sql server to use a specific one until a proper fix was deployed.