Re: [Maria-developers] mysql 5.6, 5.7

2013-06-18 Thread Roberto Spadim
hum, there's something that show the "cost" of each optimization in mariadb, like the mysql optimizer_trace? i'm thinking about the MDEV-350 about self tune coeficients, the first task is find all constants that are used in "cost" values _

Re: [Maria-developers] mysql 5.6, 5.7

2013-06-18 Thread Roberto Spadim
nice, but, debug trace put a file in system, could it be returned via sql and remove the file? (just an idea) 2013/6/18 Igor Babaev > On 06/17/2013 07:51 PM, Zardosht Kasheff wrote: > > +1 on the optimizer tracing. I have found it useful. We've had a > > couple of instances where we looked at w

Re: [Maria-developers] mysql 5.6, 5.7

2013-06-18 Thread Igor Babaev
On 06/17/2013 07:51 PM, Zardosht Kasheff wrote: > +1 on the optimizer tracing. I have found it useful. We've had a > couple of instances where we looked at where an InnoDB query plan and > TokuDB query plan diverge for some query, and it showed us bugs in our > engine. > But as an engine developer

Re: [Maria-developers] mysql 5.6, 5.7

2013-06-17 Thread Roberto Spadim
it's a nice feature not a must have feature trace what mariadb is doing in optimizer, some time (in bugs or performace problem) is nice to see what is going wrong, and why a must have feature, for me, is lock partition prune i have many myisam table with lock problem and partition lock prune can s

Re: [Maria-developers] mysql 5.6, 5.7

2013-06-17 Thread Zardosht Kasheff
+1 on the optimizer tracing. I have found it useful. We've had a couple of instances where we looked at where an InnoDB query plan and TokuDB query plan diverge for some query, and it showed us bugs in our engine. Just my $.02. -Zardosht On Mon, Jun 17, 2013 at 10:37 PM, Igor Babaev wrote: > On

Re: [Maria-developers] mysql 5.6, 5.7

2013-06-17 Thread Igor Babaev
On 06/17/2013 04:24 PM, Roberto Spadim wrote: > hi guys, i was reading mysql 5.6 and 5.7 manual > i know that mariadb is very different (a bit) than mysql internally > there's a mysql merge issue or something like that i can see what will > be merged and what not? > > i like the partition lock pru

[Maria-developers] mysql 5.6, 5.7

2013-06-17 Thread Roberto Spadim
hi guys, i was reading mysql 5.6 and 5.7 manual i know that mariadb is very different (a bit) than mysql internally there's a mysql merge issue or something like that i can see what will be merged and what not? i like the partition lock prune, memcache and optimizer tracer of mysql 5.6, but today