Doc Menu
Important

You are viewing the documentation of an older version of the TiDB database (TiDB v3.0).

It is recommended that you use the latest stable version of the TiDB database.

TiDB 3.0.11 Release Notes

Release date: March 4, 2020

TiDB version: 3.0.11

TiDB Ansible version: 3.0.11

Warning:

Some known issues are found in this version, and these issues are fixed in new versions. It is recommended that you use the latest 3.0.x version.

Compatibility Changes

  • TiDB
    • Add the max-index-length configuration item to control the maximum index length, which is compatible with the behavior of TiDB versions before 3.0.7 or of MySQL #15057

New Features

  • TiDB

    • Support showing the meta information of partitioned tables in the information_schema.PARTITIONS table #14849
  • TiDB Binlog

    • Support the bidirectional data replication between TiDB clusters #884 #909
  • TiDB Lightning

    • Support the TLS configuration #44 #270
  • TiDB Ansible

    • Modify the logic of create_users.yml so that users of the central control machine do not have to be consistent with ansible_user #1184

Bug Fixes

  • TiDB

    • Fix the issue of Goroutine leaks when retrying an optimistic transaction because queries using Union are not marked read-only #15076
    • Fix the issue that SHOW TABLE STATUS fails to correctly output the table status at the snapshot time because the value of the tidb_snapshot parameter is not correctly used when executing the SET SESSION tidb_snapshot = 'xxx'; statement #14391
    • Fix the incorrect result caused by a SQL statement that contains Sort Merge Join and ORDER BY DESC at the same time #14664
    • Fix the panic of TiDB server when creating partition tables using the unsupported expression. The error information This partition function is not allowed is returned after fixing this panic. #14769
    • Fix the incorrect result occurred when executing the select max() from subquery statement with the subquery containing Union #14944
    • Fix the issue that an error message is returned when executing the SHOW BINDINGS statement after executing DROP BINDING that drops the execution binding #14865
    • Fix the issue that the connection is broken because the maximum length of an alias in a query is 256 characters in the MySQL protocol, but TiDB does not cut the alias in the query results according to this protocol #14940
    • Fix the incorrect query result that might occur when using the string type in DIV. For instance, now you can correctly execute the select 1 / '2007' div 1 statement #14098
  • TiKV

    • Optimize the log output by removing unnecessary logs #6657
    • Fix the panic that might occur when the peer is removed under high loads #6704
    • Fix the issue that Hibernate Regions are not waken up in some cases #6732 #6738
  • TiDB Ansible

    • Update outdated document links in tidb-ansible #1169
    • Fix the issue that undefined variables might occur in the wait for region replication complete task #1173