Hello.
Maybe the output of innodb_monitor won't be truncated. Create the innodb_monitor table and check if you see the full output in the .err log. See: http://dev.mysql.com/doc/mysql/en/innodb-monitor.html Remigiusz Soko$owski <[EMAIL PROTECTED]> wrote: > Hi! > problem is not critical, however it would be nice to get some workaround > from time to time I check innodb status - the most interesting sections, > I believe, are: > FILE I/O, INSERT BUFFER AND ADAPTIVE HASH INDEX, LOG, BUFFER POOL AND > MEMORY and ROW OPERATIONS > > unfortunately they are at the bottom of whole report and that is > problem, because in one of databases I manage lock and transaction info > is so long, that other information is not displayed at all. > > Any advice? > > TIA > Remigiusz > -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.NET http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Gleb Paharenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.NET <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
