Improvements
- Upgrade the Grafana version from 7.5.7 to 7.5.11
Bug fixes
- Fix the query panic caused by overflow in the statistics module when converting a range to points for cost estimation #23625
- Fix wrong results of the control functions (such as
IF
andCASE WHEN
) when using theENUM
type data as parameters of such functions #23114 - Fix the issue that the
GREATEST
function returns inconsistent results due to different values oftidb_enable_vectorized_expression
(on
oroff
) #29434 - Fix the panic when applying index join on prefix indexes in some cases #24547
- Fix the issue that planner might cache invalid plans for
join
in some cases #28087 - Fix a bug that TiDB cannot insert
null
into a non-null column whensql_mode
is empty #11648 - Fix the wrong result type of the
GREATEST
andLEAST
functions #29019 - Fix the
privilege check fail
error when performing thegrant
andrevoke
operations to grant and revoke global level privileges #29675 - Fix the panic when using the
CASE WHEN
function on theENUM
data type #29357 - Fix wrong results of the
microsecond
function in vectorized expressions #29244 - Fix wrong results of the
hour
function in vectorized expression #28643 - Fix the issue that optimistic transaction conflicts might cause transactions to block each other #11148
- Fix the issue of incomplete log information from the
auto analyze
result #29188 - Fix the issue that using an invalid default date does not report an error when the
SQL_MODE
is 'NO_ZERO_IN_DATE' #26766 - Fix the issue that the Coprocessor Cache panel in Grafana does not display metrics. Now, Grafana displays the number of
hits
/miss
/evict
#26338 - Fix the issue that concurrently truncating the same partition causes DDL statements to stuck #26229
- Fix the issue that when the
CONCAT
function has a negative float type argument, the last digit of the argument number is chopped in the result #29417 - Fix the issue of an extra column in the query result when
NATURAL JOIN
is used to join multiple tables #29481 - Fix the issue that
TopN
is wrongly pushed down toindexPlan
whenIndexScan
uses a prefix index #29711 - Fix the issue that retrying transactions with the auto-increment columns of
DOUBLE
type causes data corruption #29892