Re: InnoDB still gives poor analysis to the optimizer

2001-12-18 Thread Philip Molter
On Tue, Dec 18, 2001 at 11:19:06PM +0200, Heikki Tuuri wrote: : Philip, : : I recommend using the MySQL STRAIGHT JOIN and USE INDEX clauses to manually : force the best plan. I'd love to, but I also have to maintain a spec of database agnosticism (which I could do in code, of course, but I shoul

Re: InnoDB still gives poor analysis to the optimizer

2001-12-18 Thread Heikki Tuuri
Philip, I recommend using the MySQL STRAIGHT JOIN and USE INDEX clauses to manually force the best plan. You could also use innodb_table_monitor to check that the key value set cardinality estimates are approximately right for the tables h, pt, and p. But to put it the other way, how could the

Re: InnoDB still gives poor analysis to the optimizer

2001-12-18 Thread Philip Molter
On Mon, Dec 17, 2001 at 10:03:58PM -0600, Philip Molter wrote: : Is there any upcoming fix for this recurring problem? The table : handler is just giving poor data to the optimizer and the optimizer : is making bad decisions because of it. It appears to come and go, : depending on data that is i

InnoDB still gives poor analysis to the optimizer

2001-12-17 Thread Philip Molter
Is there any upcoming fix for this recurring problem? The table handler is just giving poor data to the optimizer and the optimizer is making bad decisions because of it. It appears to come and go, depending on data that is in the table, what's been done, etc. To give one example, with one of o