It's a reality, Posgres' analyze output wasn't designed for the plans that EdgeQL commands can have, given the composable nature of our language. You can just d

It's a reality, Posgres' analyze output wasn't designed for the plans that EdgeQL commands can have, given the composable nature of our language. You can just do much more in one op and that balloons the plan. Not in a bad way, but you have to know how to read those things to make good understanding of it. Our goal is to streamline this for EdgeQL as much as we can.