Frank,
CREATE TABLE innodb_monitor(a INT) TYPE=InnoDB;
causes the output to be written to the .err file untruncated. DROP the table to stop the printouts.
There is a limit in the mysql client that restricts the output length to 64 kB.
Best regards,
Heikki Tuuri
Innobase Oy
Foreign keys, transactions, and row level locking for MySQL
InnoDB Hot Backup - a hot backup tool for InnoDB which also backs up MyISAM tables
http://www.innodb.com/order.php
----- Original Message ----- From: ""Dr. Frank Ullrich"" <[EMAIL PROTECTED]>
Newsgroups: mailing.database.myodbc
Sent: Monday, December 27, 2004 1:21 PM
Subject: "Show Innodb Status": Output truncated
Hi,
this is on 4.0.22-standard.
The output of "show innodb status" is truncated so that the sections FILE I/O, INSERT BUFFER AND ADAPTIVE HASH INDEX, LOG, BUFFER POOL AND MEMORY and ROW OPERATIONS are missing.
We have more than 600 concurrent connections so that the TRANSCATIONS section becomes long.
What causes that behaviour and can you work around the problem?
Regards, Frank.
--
Dr. Frank Ullrich, DBA Netzwerkadministration
Heise Zeitschriften Verlag GmbH & Co KG, Helstorfer Str. 7, D-30625 Hannover
E-Mail: [EMAIL PROTECTED]
Phone: +49 511 5352 587; FAX: +49 511 5352 538
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
-- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
