flori_ava_star:~:cursor_blinking: :made-with-estrogen: :verifiedlesbian: (@star)

@kim @wyldtom @awoo Maybe the index isn't the problem; maybe the planner is severely mis-estimating the plan, and therefore building a terrible plan? I heard that that is a thing that happens, when the analyze daemon/vacuum job hasn't been run on a table for a while for some reason

If you are really keen to find out, I'd suggest throwing the query into a very verbose explain analyze, then using a query plan visualizer to get a good overview of what the database is doing, where it is going wrong, and where most of the time in the query is spent. I actually held a workshop about this very recently :3