Comment 10 for bug 589512

Yes....

Well I remember it does not work... though it may be fixed now.
One thing I remember I was using set global use_global_long_query_time.

On Mon, Jun 7, 2010 at 11:14 AM, Oleg Tsarev <email address hidden> wrote:

> Peter,
>
> Please also read updated documentation
>
> http://www.percona.com/docs/wiki/patches:slow_extended#log_slow_slave_statements
>
> To start the logging from the slave thread, you should change the global
> value: set global log_slow_slave_statements=ON; and then execute: STOP
> SLAVE; START SLAVE;. This will destroy and recreate the slave SQL
> thread, so it will see the newly set global value.
>
> To stop the logging from the slave thread, you should just change the
> global value: set global log_slow_slave_statements=OFF; and the logging
> stop immediately.
>
> --
> make log_slave_slow_statements run time global variable
> https://bugs.launchpad.net/bugs/589512
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Percona Server with XtraDB: Invalid
>
> Bug description:
> currently log-slow-slave-statements is only startup variable. It has to be
> changed to be global run time settable variable and added to SHOW VARIABLES
> list.
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/percona-server/+bug/589512/+subscribe
>

--
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

Percona Training Workshops
http://www.percona.com/training/