Currently the join cost model only exposes the total cost for each stage in the plan. During development and debugging this cost is not sufficient to understand which part of the cost model is contributing to the cost the most (cpu, sequential or random IO). It would be help to expose all of these components in explain so we can debug optimizer decisions via explain directly without needing to turn on verbose logging and digging through them, which can become difficult even with 4+ tables.