No actually I believe that cacheable was always traceable to the case where we were inferring the partitioning, but it was just more difficult to do that tracing. The exception might have been some planner test cases where we were being sloppy about the input settings and they happened to have no effect on the resulting plan.