TiDB 3.0.6 release, NewSQL distributed database

TiDB 3.0.6 has been released, updated as follows:

• SQL optimizer
  • After the repair window function AST Restore SQL text result is not correct the problem, over w it should not be restore to  over (w) # 12933
  • Repair stream aggregation pushed down to double read question  # 12690
  • Issues that are fixed in SQL bind handle incorrect quotes  # 13117
  • Optimization  select max(_tidb_rowid) from t scene, avoid full table scan  # 13095
  • When the repair query contains a variable assignment expression query results are incorrect question  # 13231
  • Repair  UPDATE statement contains errors result when the sub-queries and problems generated column; repair  UPDATE when the same table statement contains two different database table names, UPDATE execution error problem  # 13350
  • With the support  _tidb_rowid to do the investigation  # 13416
  • Repair partition table statistics error leads to generate an execution plan using an incorrect question  # 13628
• SQL execution engine
  • Repair is not compatible with the type of year for processing and MySQL invalid value problem  # 12745
  • In the  INSERT ON DUPLICATE UPDATE statement multiplexing  Chunk to reduce memory overhead  # 12998
  • Add built-in functions  JSON_VALID support  # 13133
  • Support in the implementation of the partition table  ADMIN CHECK TABLE # 13140
  • Repair of empty tables  FAST ANALYZE when panic problem  # 13343
  • Repair panic when performing Fast Analyze problems on an empty table contains a multi-column index  # 13394
  • When fix  WHERE the problem when there is equivalence condition UNIQUE KEY clause on the estimated number of rows is greater than 1,  # 13382
  • When TiDB open repair  Streaming problems after returning data may be duplicated  # 13254
  • The  CMSketch largest number of N values appearing extracted improve estimation accuracy  # 13429
• Server
  • When gRPC request timed out in advance so that requests to TiKV failure  # 12926
  • Add the following virtual table: # 13009
    • performance_schema.tidb_profile_allocs
    • performance_schema.tidb_profile_block
    • performance_schema.tidb_profile_cpu
    • performance_schema.tidb_profile_goroutines
  • Fix the problem query while waiting pessimistic locking, kill query does not take effect  # 12989
  • When the lock fails pessimistic transactions, and the transaction involves only modify a key is no longer asynchronous rollback  # 12707
  • Repair split Region request response is empty panic problem  # 13092
  • When pessimistic transactions in other transactions leading to the first locked lock failure, avoid duplication backoff  # 13116
  • When you modify the behavior of TiDB check the configuration, does not recognize the configuration options appear, print the warning log  # 13272
  • Support by  /info/all acquiring all TiDB node interfaces binlog status  # 13187
  • Goroutine possible leak repair kill connection problems  # 13251
  • Let the  innodb_lock_wait_timeout parameters take effect in the pessimistic transactions for controlling pessimistic locking and other lock timeout  # 13165
  • When the query is pessimistic transactions kill, stop TTL update pessimistic transactions, and other transactions avoid doing unnecessary waiting  # 13046
• DDL
  • Repair  SHOW CREATE VIEW results inconsistent with MySQL problem  # 12912
  • UNION supports creation View, for example,  create view v as select * from t1 union select * from t2 # 12955
  • To the  slow_query table to add more business-related fields: # 13072
    • Prewrite_time
    • Commit_time
    • Get_commit_ts_time
    • Commit_backoff_time
    • Backoff_types
    • Resolve_lock_time
    • Local_latch_wait_time
    • Write_key
    • Write_size
    • Prewrite_region
    • Txn_retry
  • When you create a table if the table contains a column using the collate collate the table rather than the system default character set  # 13174
  • Limit index name when creating the table length  # 13310
  • Check the length of the table name is not a problem when the Table to repair the rename  # 13346
  • New  alter-primary-key configuration to support TiDB add / drop primary key, this configuration is disabled by default  # 13522

TiKV

• Fix  acquire_pessimistic_lock the interface returns an error  txn_size question  # 5740
• Restrictions GC worker writes per second to reduce the impact on performance  # 5735
• Optimized lock manager accuracy  # 5845
• Pessimistic locking support  innodb_lock_wait_timeout # 5848
• Adding Titan configuration detection  # 5720
• Support with tikv-ctl dynamically modify the GC limiting configuration: tikv-ctl --host=ip:port modify-tikv-config -m server -n gc.max_write_bytes_per_sec -v 10MB # 5957
• Reducing unnecessary clean up the request, reducing the pressure of deadlock detector  # 5965
• Avoid TTL time is shortened pessimistic transactions prewrite  # 6056
• Titan missing blob file repair problems that may occur  # 5968
• Titan may lead to restoration  RocksDBOptions does not take effect issue  # 6009

PD

• Each filter is called to add a  ActOn new dimension to indicate the effect of each filter received checker and scheduler. Delete unused two filters: disconnectFilter and  rejectLeaderFilter # 1911
• When PD generated time stamps exceeds 5 milliseconds, a warning will print log  # 1867
• When there endpoint is unavailable, reduce client log level  # 1856
• Repair  region_syncer synchronization gRPC packet may be too big of a problem  # 1952

Tools

• TiDB Binlog
  • Drainer configured  initial-commit-ts to -1, the initial synchronization acquisition time stamp from the PD  # 788
  • Drainer checkpoint storage and downstream decoupled support options to configure checkpoint save to a local file or MySQL  # 790
  • Drainer fix the problem in configuration synchronization filtering database table with an empty value causes a Panic  # 801
  • Repair Drainer because failure to downstream applications Binlog and after Panic process does not quit but locks up the issue  # 807
  • Pump repair off the assembly line because gRPC of  GracefulStop processes and hang live issue  # 817
  • Repair Drainer performed TiDB  DROP COLUMN received during DDL problem binlog a lack of synchronization and error (requires TiDB 3.0.6 above) # 827
• TiDB Lightning
  • New TiDB Backend mode  max-allowed-packet configuration items, the default value is 64M  # 248

Details: https://pingcap.com/docs-cn/stable/releases/3.0.6/