MySQL Native Driver (
Mysqlnd
)
2536
Statistic Scope
Description
Notes
there is an error reading the result set
header packet from the line.
non_result_set_queries
Connection
Number of queries that did not generate
a result set. Examples of queries that
do not generate a result set:
INSERT
,
UPDATE
,
LOAD DATA
,
SHOW
. The
statistic will not be incremented if there
is an error reading the result set header
packet from the line.
You may use it as an indirect measure
for the number of queries PHP has sent
to MySQL, for example, to identify a
client that causes a high database load.
no_index_used
Connection
Number of queries that have
generated a result set but did not
use an index (see also mysqld
start option –log-queries-not-
using-indexes). If you want these
queries to be reported you can use
mysqli_report(MYSQLI_REPORT_INDEX)
to make ext/mysqli throw an
exception. If you prefer a warning
instead of an exception use
mysqli_report(MYSQLI_REPORT_INDEX
^ MYSQLI_REPORT_STRICT).
bad_index_used
Connection
Number of queries that have generated
a result set and did not use a good
index (see also mysqld start option –
log-slow-queries).
If you want these queries
to be reported you can use
mysqli_report(MYSQLI_REPORT_INDEX)
to make ext/mysqli throw an
exception. If you prefer a warning
instead of an exception use
mysqli_report(MYSQLI_REPORT_INDEX
^ MYSQLI_REPORT_STRICT)
slow_queries
Connection
SQL statements that took more
than
long_query_time
seconds
to execute and required at least
min_examined_row_limit
rows to
be examined.
Not reported through
mysqli_report
buffered_sets
Connection
Number of buffered result sets returned
by “normal” queries. “Normal” means
“not prepared statement” in the
following notes.
Examples of API calls that will
buffer result sets on the client:
mysql_query
,
mysqli_query
,
mysqli_store_result
,
mysqli_stmt_get_result
. Buffering
result sets on the client ensures that
server resources are freed as soon
as possible and it makes result set
scrolling easier. The downside is the
additional memory consumption on
the client for buffering data. Note that
mysqlnd (unlike the MySQL Client
Library) respects the PHP memory limit
because it uses PHP internal memory
management functions to allocate
memory. This is also the reason why
memory_get_usage
reports a higher
memory consumption when using
mysqlnd instead of the MySQL Client
Library.
memory_get_usage
does not
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 ...