MySQL Native Driver (
Mysqlnd
)
2537
Statistic Scope
Description
Notes
measure the memory consumption of
the MySQL Client Library at all because
the MySQL Client Library does not use
PHP internal memory management
functions monitored by the function!
unbuffered_sets
Connection
Number of unbuffered result sets
returned by normal (non prepared
statement) queries.
Examples of API calls that will not
buffer result sets on the client:
mysqli_use_result
ps_buffered_sets
Connection
Number of buffered result sets returned
by prepared statements. By default
prepared statements are unbuffered.
Examples of API calls that will not
buffer result sets on the client:
mysqli_stmt_store_result
ps_unbuffered_sets
Connection
Number of unbuffered result sets
returned by prepared statements.
By default prepared statements are
unbuffered.
flushed_normal_sets
Connection
Number of result sets from normal
(non prepared statement) queries with
unread data which have been flushed
silently for you. Flushing happens only
with unbuffered result sets.
Unbuffered result sets must be
fetched completely before a new
query can be run on the connection
otherwise MySQL will throw an
error. If the application does not
fetch all rows from an unbuffered
result set, mysqlnd does implicitly
fetch the result set to clear the line.
See also
rows_skipped_normal
,
rows_skipped_ps
. Some possible
causes for an implicit flush:
• Faulty client application
• Client stopped reading after it found
what it was looking for but has made
MySQL calculate more records than
needed
• Client application has stopped
unexpectedly
flushed_ps_sets
Connection
Number of result sets from prepared
statements with unread data which
have been flushed silently for you.
Flushing happens only with unbuffered
result sets.
Unbuffered result sets must be
fetched completely before a new
query can be run on the connection
otherwise MySQL will throw an
error. If the application does not
fetch all rows from an unbuffered
result set, mysqlnd does implicitly
fetch the result set to clear the line.
See also
rows_skipped_normal
,
rows_skipped_ps
. Some possible
causes for an implicit flush:
• Faulty client application
• Client stopped reading after it found
what it was looking for but has made
MySQL calculate more records than
needed
• Client application has stopped
unexpectedly
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 ...