Skip to content

Latest commit

 

History

History
70 lines (70 loc) · 3.46 KB

tidb_bugs.md

File metadata and controls

70 lines (70 loc) · 3.46 KB
Raw

Reported Bugs in TiDB

  • TiDB produces different results for SELECT statement when using transaction
  • TiDB loses connection when executing transaction
  • Malicious SQL statement which directly crashes TiDB server by triggering stack overflow
  • Unrepeatable read occurs when two transaction are executed
  • TiDB produces different results for SELECT statement when using transaction which uses update stmt
  • TiDB fails to insert data when using transaction
  • TiDB produces different results for SELECT statements (Subquery returns more than 1 row)
  • TiDB loses connection when using transaction
  • insert's SET opration or VALUES_LIST doesn't support the subquery correctly
  • TiDB server is killed because of "out of memory (OOM)"
  • TiDB connection is lost due to "invalid memory address or nil pointer dereference"
  • TiDB produces different results for DELETE statements (Division by 0)
  • TiDB (with tikv) hangs when processing SELECT statement
  • ROLLBACK transaction affects the result of COMMIT transaction in TiDB (with TiKV)
  • "Lost connection to MySQL server during query" after UPDATE statement
  • TiDB produces different results for SELECT statements (BIGINT value is out of range in '(8 - 100)')
  • Malicious SQL statement which directly crashes TiDB server by triggering stack overflow
  • TiDB (with tikv) produces different results for SELECT statements when using transaction
  • Strange transaction results caused by "Truncated incorrect INTEGER value"
  • Inconsistent read and write, which use the same predicate (WHERE clause)
  • Lost connection to MySQL server during query (tidb/executor.(*baseJoiner).makeJoinRowToChunk)
  • Undetermined results of the SELECT statement with CTE
  • TiDB produces different results for SELECT statements (runtime error: index out of range [0] with length 0)