Maximilian Hoffman

Yes the main issue is the join order, which will only be in that feature branch for now. Moving the condition to a `WHERE` will be unnecessary after I am...

You should usually file a bug before resorting to this, but you also manually set the join order with `SELECT /*+ JOIN_ORDER(pa, p, ib, obj, o, ik, ki) */ count(*)...

I need to rewrite join ordering generation to get the final edge cases. I hope to finish by Friday.

@knutwannheden I ended up rewriting our join ordering algorithm to fix this. I am currently working on adding our missing join operators, SemiJoin, AntiJoin, FullOuterJoin to make it easier to...

The new runtime with the joins PR (https://github.com/dolthub/go-mysql-server/pull/1290.) and pending up subquery bug fix (https://github.com/dolthub/go-mysql-server/pull/1350) should be more satisfactory, though there is more room for improving the join plan when...

Release `0.50.9` is out, thank you for the quality of your repros, and let me know when you find more issues. Keep in mind 1) we do not consider filters...

Look at how i fixed this for setup scripts. The files need to be loaded into Go structs that can be accessed from GMS and integrator.

It was written specifically to boost perf for old format index joins, so I'm not sure now is the time to merge this. It is pure drag on the new...

#benchmark

`joinIndexes.getUsableIndex` currently returns the first index it finds that prefixes the join condition column. We would need the other filters in the above case at the time we select a...