MDEV-21383 fixed the issue with possible range plans not being used for inner joins.
Now, I am observing a similar issue for nested outer joins.
(I can't attach a testcase, because I don't have it atm. I have customer table DDLs and optimizer_trace. I've made a patch which fakes the optimizer stats and records_in_range() return values, and then I can see a bad query plan to be generated).
Checking my testcase against other server versions:
- The issue is not reproducible before the patch for
- The issue is not reproducible with the original, "conservative" patch for