标签:COUNT operations rows count InnoDB student SELECT
MySQL :: MySQL 8.0 Reference Manual :: 12.20.1 Aggregate Function Descriptions https://dev.mysql.com/doc/refman/8.0/en/aggregate-functions.html#function_count
-
Returns a count of the number of non-
NULL
values ofexpr
in the rows retrieved by aSELECT
statement. The result is aBIGINT
value.If there are no matching rows,
COUNT()
returns0
.COUNT(NULL)
returns 0.This function executes as a window function if
over_clause
is present.over_clause
is as described in Section 12.21.2, “Window Function Concepts and Syntax”.mysql> SELECT student.student_name,COUNT(*) FROM student,course WHERE student.student_id=course.student_id GROUP BY student_name;
COUNT(*)
is somewhat different in that it returns a count of the number of rows retrieved, whether or not they containNULL
values.For transactional storage engines such as
InnoDB
, storing an exact row count is problematic. Multiple transactions may be occurring at the same time, each of which may affect the count.InnoDB
does not keep an internal count of rows in a table because concurrent transactions might “see” different numbers of rows at the same time. Consequently,SELECT COUNT(*)
statements only count rows visible to the current transaction.As of MySQL 8.0.13,
SELECT COUNT(*) FROM
query performance fortbl_name
InnoDB
tables is optimized for single-threaded workloads if there are no extra clauses such asWHERE
orGROUP BY
.InnoDB
processesSELECT COUNT(*)
statements by traversing the smallest available secondary index unless an index or optimizer hint directs the optimizer to use a different index. If a secondary index is not present,InnoDB
processesSELECT COUNT(*)
statements by scanning the clustered index.Processing
SELECT COUNT(*)
statements takes some time if index records are not entirely in the buffer pool. For a faster count, create a counter table and let your application update it according to the inserts and deletes it does. However, this method may not scale well in situations where thousands of concurrent transactions are initiating updates to the same counter table. If an approximate row count is sufficient, useSHOW TABLE STATUS
.InnoDB
handlesSELECT COUNT(*)
andSELECT COUNT(1)
operations in the same way. There is no performance difference.For
MyISAM
tables,COUNT(*)
is optimized to return very quickly if theSELECT
retrieves from one table, no other columns are retrieved, and there is noWHERE
clause. For example:mysql> SELECT COUNT(*) FROM student;
This optimization only applies to
MyISAM
tables, because an exact row count is stored for this storage engine and can be accessed very quickly.COUNT(1)
is only subject to the same optimization if the first column is defined asNOT NULL
. -
COUNT(DISTINCT
expr
,[expr
...])Returns a count of the number of rows with different non-
NULL
expr
values.If there are no matching rows,
COUNT(DISTINCT)
returns0
.mysql> SELECT COUNT(DISTINCT results) FROM student;
In MySQL, you can obtain the number of distinct expression combinations that do not contain
NULL
by giving a list of expressions. In standard SQL, you would have to do a concatenation of all expressions insideCOUNT(DISTINCT ...)
.
MySQL :: MySQL 8.0 Reference Manual :: 3.3.4.8 Counting Rows https://dev.mysql.com/doc/refman/8.0/en/counting-rows.html
MySQL :: MySQL 8.0 Reference Manual :: 13.7.7.38 SHOW TABLE STATUS Statement https://dev.mysql.com/doc/refman/8.0/en/show-table-status.html
Rows
The number of rows. Some storage engines, such as MyISAM
, store the exact count. For other storage engines, such as InnoDB
, this value is an approximation, and may vary from the actual value by as much as 40% to 50%. In such cases, use SELECT COUNT(*)
to obtain an accurate count.
The Rows
value is NULL
for INFORMATION_SCHEMA
tables.
For InnoDB
tables, the row count is only a rough estimate used in SQL optimization. (This is also true if the InnoDB
table is partitioned.)
标签:COUNT,operations,rows,count,InnoDB,student,SELECT 来源: https://www.cnblogs.com/rsapaper/p/16527204.html
本站声明: 1. iCode9 技术分享网(下文简称本站)提供的所有内容,仅供技术学习、探讨和分享; 2. 关于本站的所有留言、评论、转载及引用,纯属内容发起人的个人观点,与本站观点和立场无关; 3. 关于本站的所有言论和文字,纯属内容发起人的个人观点,与本站观点和立场无关; 4. 本站文章均是网友提供,不完全保证技术分享内容的完整性、准确性、时效性、风险性和版权归属;如您发现该文章侵犯了您的权益,可联系我们第一时间进行删除; 5. 本站为非盈利性的个人网站,所有内容不会用来进行牟利,也不会利用任何形式的广告来间接获益,纯粹是为了广大技术爱好者提供技术内容和技术思想的分享性交流网站。