Last week we saw Uber’s move away from Postgres to MySQL get a lot of attention. This week we get a few well reasoned responses from the Postgres community which include some areas we can improve, as well as some highlights of why what they were trying to do didn’t make as much sense in Postgres.
You’ve added the INDEXes, both partial and covering. You’ve VACCUUM ANALYZEd. You JOINed and INNER JOINed everything to a single query. And yet, your report is still taking too long. What do you do when the low-hanging fruit has been harvested?
We know the frustration. You see all the places your app could be so much better, but you can't seem to convince your boss. Next time, mention Corgibytes. Our Code Inspection™ can help you explain technical improvements in a way executives can understand.