I can reproduce this >5 execution plan change with a prepared statement for this min/max query indeed. I'm not sure SpiceDB uses prepared statements though, but I'm hopeful this is zeroing in on the root cause. Maybe this behaviour is not only used for prepared statements