Comment 7 for bug 592365

each background threads have different role and process.
So common columns are not useful to analyze problems, if occur. (or mess, "info" contains particle of "show innodb status"?)
Almost empty for me.

I don't agree useless i_s only to satisfy your curiosity, and to support it forever.
I don't believe person who don't read "show innodb status" can read when it is in i_s.

However you say "show innodb status" mess, for me, it is the best information to solve performance problem.
In this case, i_s is more mess than show innodb status.
I think why you feel mess is because you don't understand InnoDB, e.g. you suggested to include InnoDB_trx_id to the "thread".

The performance problem should be solved by totally viewing.
I don't believe such limited i_s solves something.

Please explain for what such information is useful.
Please explain what information should be included to the i_s concretely?

Do you think how the different items into common format of the i_s? without filtered? without twisted?
I always need raw information from InnoDB.
e.g. current information about master thread (5.5)
---------
srv_master_thread loops: 1 1_second, 1 sleeps, 0 10_second, 1 background, 1 flush
srv_master_thread log flush and writes: 1
---------