Skip to content

Latest commit

 

History

History
39 lines (31 loc) · 2.02 KB

release-2.0-rc.4.md

File metadata and controls

39 lines (31 loc) · 2.02 KB
title aliases summary
TiDB 2.0 RC4 Release Notes
/docs/dev/releases/release-2.0-rc.4/
/docs/dev/releases/2rc4/
TiDB 2.0 RC4, released on March 30, 2018, brings improvements in MySQL compatibility, SQL optimization, and stability. Key updates include support for various syntax, bug fixes, and performance optimizations in TiDB, PD, and TiKV. Notable changes include manual Region splitting in PD, memory usage limitation in TiKV, and support for data pattern import. Overall, the release focuses on enhancing functionality and addressing performance issues.

TiDB 2.0 RC4 Release Notes

On March 30, 2018, TiDB 2.0 RC4 is released. This release has great improvement in MySQL compatibility, SQL optimization and stability.

TiDB

  • Support SHOW GRANTS FOR CURRENT_USER();
  • Fix the issue that the Expression in UnionScan is not cloned
  • Support the SET TRANSACTION syntax
  • Fix the potential goroutine leak issue in copIterator
  • Fix the issue that admin check table misjudges the unique index including null
  • Support displaying floating point numbers using scientific notation
  • Fix the type inference issue during binary literal computing
  • Fix the issue in parsing the CREATE VIEW statement
  • Fix the panic issue when one statement contains both ORDER BY and LIMIT 0
  • Improve the execution performance of DecodeBytes
  • Optimize LIMIT 0 to TableDual, to avoid building useless execution plans

PD

  • Support splitting Region manually to handle the hot spot in a single Region
  • Fix the issue that the label property is not displayed when pdctl runs config show all
  • Optimize metrics and code structure

TiKV

  • Limit the memory usage during receiving snapshots, to avoid OOM in extreme conditions
  • Support configuring the behavior of Coprocessor when it encounters warnings
  • Support importing the data pattern in TiKV
  • Support splitting Region in the middle
  • Increase the speed of CI test
  • Use crossbeam channel
  • Fix the issue that too many logs are output caused by leader missing when TiKV is isolated