maria-developers team mailing list archive
-
maria-developers team
-
Mailing list archive
-
Message #00359
Re: microslow-innodb ported to 5.1
OK. This is reasonable. So why do not we convert our current Innodb and
execution plan items to status variables and do not get this functionality
to write them to the log
> Over time we will have more and more variables and I don't think it
> makes sense to log all changes to the slow log.
>
> I don't think it's hard to maintain a list of what to log.
>
>
--
Peter Zaitsev, CEO, Percona Inc.
Tel: +1 888 401 3401 ext 501 Skype: peter_zaitsev
24/7 Emergency Line +1 888 401 3401 ext 911
References
-
microslow-innodb ported to 5.1
From: Vadim Tkachenko, 2009-05-27
-
Re: microslow-innodb ported to 5.1
From: Arjen Lentz, 2009-05-27
-
Re: microslow-innodb ported to 5.1
From: Michael Widenius, 2009-05-27
-
Re: microslow-innodb ported to 5.1
From: Vadim Tkachenko, 2009-05-28
-
Re: microslow-innodb ported to 5.1
From: Sergei Golubchik, 2009-05-28
-
Re: microslow-innodb ported to 5.1
From: Vadim Tkachenko, 2009-05-28
-
Re: microslow-innodb ported to 5.1
From: Sergei Golubchik, 2009-05-31
-
Re: microslow-innodb ported to 5.1
From: Peter Zaitsev, 2009-06-03
-
Re: microslow-innodb ported to 5.1
From: Sergei Golubchik, 2009-06-03
-
Re: microslow-innodb ported to 5.1
From: Michael Widenius, 2009-06-04