InnoDB
Performance Tuning and Troubleshooting
1295
COLUMNS: par_id: DATA_INT len 4 prec 0;
fname: DATA_CHAR prtype 524542 len 20 prec 0;
lname: DATA_CHAR prtype 524542 len 20 prec 0;
DB_ROW_ID: DATA_SYS prtype 256 len 6 prec 0;
DB_TRX_ID: DATA_SYS prtype 257 len 6 prec 0;
DB_ROLL_PTR: DATA_SYS prtype 258 len 7 prec 0;
INDEX: name PRIMARY, id 0 15, fields 1/5, type 3
root page 50, appr.key vals 299, leaf pages 2, size pages 3
FIELDS: par_id DB_TRX_ID DB_ROLL_PTR fname lname
INDEX: name lname, id 0 16, fields 2/3, type 2
root page 51, appr.key vals 300, leaf pages 1, size pages 1
FIELDS: lname fname par_id
FOREIGN KEY CONSTRAINT test/child_ibfk_1: test/child ( par_id )
REFERENCES test/parent ( par_id )
-----------------------------------
END OF INNODB TABLE MONITOR OUTPUT
==================================
For each table, Table Monitor output contains a section that displays general information about the
table and specific information about its columns, indexes, and foreign keys.
The general information for each table includes the table name (in
db_name/tbl_name
format except
for internal tables), its ID, the number of columns and indexes, and an approximate row count.
The
COLUMNS
part of a table section lists each column in the table. Information for each column
indicates its name and data type characteristics. Some internal columns are added by
InnoDB
, such
as
DB_ROW_ID
(row ID),
DB_TRX_ID
(transaction ID), and
DB_ROLL_PTR
(a pointer to the rollback/
undo data).
•
DATA_xxx
: These symbols indicate the data type. There may be multiple
DATA_xxx
symbols for a
given column.
•
prtype
: The column's “precise” type. This field includes information such as the column data type,
character set code, nullability, signedness, and whether it is a binary string. This field is described in
the
innobase/include/data0type.h
source file.
•
len
: The column length in bytes.
•
prec
: The precision of the type.
Each
INDEX
part of the table section provides the name and characteristics of one table index:
•
name
: The index name. If the name is
PRIMARY
, the index is a primary key. If the name is
GEN_CLUST_INDEX
, the index is the clustered index that is created automatically if the table
definition doesn't include a primary key or non-
NULL
unique index. See
Section 14.2.9.1, “Clustered
and Secondary Indexes”
.
•
id
: The index ID.
•
fields
: The number of fields in the index, as a value in
m/n
format:
•
m
is the number of user-defined columns; that is, the number of columns you would see in the
index definition in a
CREATE TABLE
statement.
•
n
is the total number of index columns, including those added internally. For the clustered index,
the total includes the other columns in the table definition, plus any columns added internally. For
a secondary index, the total includes the columns from the primary key that are not part of the
secondary index.
•
type
: The index type. This is a bit field. For example, 1 indicates a clustered index and 2 indicates a
unique index, so a clustered index (which always contains unique values), will have a
type
value of
3. An index with a
type
value of 0 is neither clustered nor unique. The flag values are defined in the
innobase/include/dict0mem.h
source file.
•
root page
: The index root page number.
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...