Thanks,
It does look like an incorrect prediction. Looking again, I think it's the row
estimate for the join that's out - the planner estimates one row returned, in
which case a nested join would probably make sense, whereas in fact there are
23.
However it's a generated (user created) query,
Hi,
I have a query I'm trying to optimise. It takes just under a second to run, not
too bad for my users but I'm worried that as the size of the data increases, it
will get worse. Of course the plan may change when that happens but I'd also
like to learn a bit more about optimisation anyway.
T
