Re: BUG #18261: Inconsistent results of SELECT affected by joined subqueries

Hmm, I don't think the insert statement in the test case is redundant.
It's needed to verify that the query in the test case gives the correct
result.  Without the insert statement, the wrong plan would give the
same result as the correct plan, i.e., an empty set in this case.

IMO, if we make some code changes and add a test case for that, we need
to ensure the test can give a different (and correct of course) result
than what came before.

Thanks
Richard