TiDB 3.0.8 release, NewSQL distributed database

TiDB  3.0.8  has been released, this version updates are as follows:

TiDB

• SQL optimizer
  • Repair SQL Binding because the cache is not updated in a timely manner, resulting in the binding plan wrong question  # 13891
  • Fix the problem when SQL contains list of symbols (like "?,?,?" This placeholder), SQL Binding may fail  # 14004
  • Since the original SQL repair SQL Binding to  ; the end of the problem and not create / delete  # 14113
  • Repair  PhysicalUnionScan operator is not set correctly statistics, query plans may lead to problems of wrong  # 14133
  • Removing  minAutoAnalyzeRatio constraints to automatically analyze the more timely  # 14015
• SQL execution engine
  • Fix  INSERT/REPLACE/UPDATE ... SET ... = DEFAULT the problem syntax error, repair,  DEFAULT expressions and generate virtual column with the question of the use will complain  # 13682
  • Repair  INSERT statement during question time string type to convert floating-point type, may be error of  # 14011
  • Repair  HashAgg Executor concurrency value is not properly initialized, resulting in polymerization operation is performed in some cases the problem of low efficiency  # 13811
  • Executive being given repair group by item be included in brackets  # 13658
  • Repair TiDB not calculated group by the right item, cause problems OUTER JOIN execution will complain some cases  # 14014
  • Fix a problem beyond the outer Range Range of data written to the partition table, the error message inaccurate  # 14107
  • In view of the upcoming MySQL 8 abandoned  PadCharToFullLength, Revert PR  # 10124  and revoke  PadCharToFullLength effect, in order to avoid some special cases the query results do not meet expectations  # 14157
  • Repair  ExplainExec does not guarantee  close() call which led to  EXPLAIN ANALYZE problems caused by leakage when goroutine  # 14226
• DDL
  • Optimization "change column" / "modify column " error message is output, are easier to understand  # 13796
  • New  SPLIT PARTITION TABLE syntax to support the partition table Region segmentation function  # 13929
  • Repair create an index, not properly check the length, resulting in the index longer than 3072 bytes no problem being given  # 13779
  • Due to repair partition table add an index if it takes too long, it may lead to output  GC life time is shorter than transaction duration an error message problem  # 14132
  • Repair  DROP COLUMN/ MODIFY COLUMN/ CHANGE COLUMN no foreign key checks when executed cause  SELECT * FROM information_schema.KEY_COLUMN_USAGE problems panic occurs when the statement  # 14105
• Server
  • Statement Summary Improvements:
    • Add a large number of SQL index fields, SQL facilitate a more detailed statistical analysis  # 14151 , # 14168
    • New  stmt-summary.refresh-interval parameters for controlling the periodic  events_statements_summary_by_digest table of expired data to the  events_statements_summary_by_digest_history tables, the default interval: for 30 min  # 14161
    • New  events_statements_summary_by_digest_history table, save from the  events_statements_summary_by_digest expiration of the data  # 14166
  • Repair internal SQL execution RBAC related error output binlog question  # 13890
  • New  server-version configuration item to modify TiDB server version control function  # 13906
  • New recovery TiDB binlog write functionality through an HTTP interface  # 13892
  • The  GRANT roles TO user permissions required by the  GrantPriv modification to  ROLE_ADMIN or  SUPERto be consistent with the MySQL  # 13932
  • When  GRANT the time statement does not specify the database name, TiDB behavior changed by the use of the current database error  No database selected, maintaining compatibility with MySQL  # 13784
  • Modify  REVOKE the statement execute permissions from the  SuperPriv changed user only needs to have the proper permission Schema, you can execute  REVOKE the statement, consistent with the MySQL  # 13306
  • Repair  GRANT ALL grammar in no  WITH GRANT OPTION time, erroneously  GrantPriv issue authorization to the target user  # 13943
  • Repair  LoadDataInfo call  addRecord when an error, the error message does not contain lead to  LOAD DATA the behavior of statements incorrect information in question  # 13980
  • Repair due to query multiple SQL statements share the same  StartTime problems led to slow query output error information  # 13898
  • Fix  batchClient problem can cause a memory leak when processing large transaction  # 14032
  • Repair  system_time_zone fixed appears as  CST a problem, and now TiDB of  system_time_zone will from  mysql.tidb the table  systemTZ to obtain  # 14086
  • Repair  GRANT ALL grammar grant permissions incomplete (eg  Lock_tables_privissues)  # 14092
  • Repair  Priv_create_user permissions can not  CREATE ROLE and  DROP ROLEquestion  # 14088
  • The  ErrInvalidFieldSize error code from the  1105(Unknow Error) changed  3013 # 13737
  • New  SHUTDOWN command stops TiDB Server, and add  ShutdownPriv authority  # 14104
  • Repair  DROP ROLE when fails, some of the ROLE still be unexpectedly deleted atomic problem statement, avoid statements  # 14130
  • The following repair 3.0 version upgrade to 3.0, tidb_enable_window_function the  SHOW VARIABLE query results statement error output to question 1, the output after the repair 0  # 14131
  • Repair TiKV node offline, due to the  gcworker continuous retry may lead to leakage problems goroutine  # 14106
  • Binlog recorded in the log slow  Prewrite time, enhance the ease of tracing the problem  # 14138
  • tidb_enable_table_partition GLOBAL SCOPE supports variable scoping  # 14091
  • Not properly correspond to the new privileges granted permission to repair the new user results in user rights may be missing or mistakenly added problem  # 14178
  • When TiKV repair broken links, due  rpcClient not close, causing  CheckStreamTimeoutLoop goroutine leak problem  # 14227
  • Support for certificate-based authentication ( using the document ) # 13955
• Transaction
  • When you create a new cluster, tidb_txn_mode the default value of the variable by  "" changed  "pessimistic" # 14171
  • The problem of long time to fix pessimistic lock transaction mode, retry the transaction such as a single statement of lock time is not reset cause, etc.  # 13990
  • Repair pessimistic transaction mode, because the data have not changed unlocked may lead to incorrect data read question  # 14050
  • Repair mocktikv in prewrite, does not distinguish between types of transactions, resulting in duplicate insert value constraint checking  # 14175
  • Repair  session.TxnState status  Invalid when the transaction could not be processed correctly problems caused panic  # 13988
  • Repair mocktikv the  ErrConfclit structure does not contain  ConflictCommitTS issues  # 14080
  • After repair TiDB Resolve Lock, did not correctly handle lock-out check cause problems Affairs jammed  # 14083
• Monitor
  • LockKeys New  pessimistic_lock_keys_duration monitoring  # 14194

TiKV

• Coprocessor
  • Coprocessor modify the output log an error is encountered from level  error change  warn # 6051
  • Modify statistics update behavior of sampled data from the first drop and insert directly into the line more, the update behavior is consistent with tidb-server  # 6069
• Raftstore
  • Repeat repair due to  peerfsm send a message destory, peerfsm was repeatedly destroyed causing the problem of panic  # 6297
  • split-region-on-table The default value of  true change  false, the default table by slicing off function Region  # 6253
• Engine
  • Under extreme conditions due to repair RocksDB iterator error is not handled correctly may lead to problems of data returned empty  # 6326
• Affairs
  • Repair pessimistic lock because the lock is not properly cleaned resulting in Key can not be written, and the problem of stuck GC  # 6354
  • Optimization pessimistic locks and other locking mechanism, enhance the scene of serious conflict lock performance  # 6296
• The default value of the memory allocation library  tikv_alloc/default into  jemalloc # 6206

PD

• Client
  • Added by  context can set the timeout when creating new client, create a new Client  # 1994
  • Create a new  KeepAlive connection features  # 2035
• Optimization /api/v1/regions API performance  # 1986
• Repair deleted  tombstone state Store may cause panic risks  # 2038
• Region fix the problem when loading information from disk errors will range overlapping Region deleted  # 2011 , # 2040
• After etcd upgrade from version 3.4.0 to 3.4.3 stable version, note that the upgrade can only be downgraded by pd-recover tool  # 2058

Tools

• TiDB Binlog
  • Pump repair the absence of receipt of the DDL commit binlog lead binlog neglected issue  # 853

TiDB Ansible

• Rollback is streamlined configuration item  # 1053
• When optimizing rolling upgrade TiDB version checking logic  # 1056
• TiSpark upgrade to version 2.1.8  # 1061
• PD monitoring items on the page Role repair Grafana monitor display incorrect question  # 1065
• Optimization TiKV Detail page on Grafana surveillance  Thread Voluntary Context Switches and  Thread Nonvoluntary Context Switches monitoring item  # 1071

details:

https://pingcap.com/docs-cn/stable/releases/3.0.8/

https://github.com/pingcap/tidb/releases/tag/v3.0.8