From bfd73cee1a75f70499eee490d2a4c0d6161adacf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dani=C3=ABl=20van=20Eeden?= Date: Tue, 23 Sep 2025 09:38:56 +0200 Subject: [PATCH 1/4] sql-statement-create-binding: add note about truncation --- sql-statements/sql-statement-create-binding.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/sql-statements/sql-statement-create-binding.md b/sql-statements/sql-statement-create-binding.md index 7788679e68967..cd474b90e506d 100644 --- a/sql-statements/sql-statement-create-binding.md +++ b/sql-statements/sql-statement-create-binding.md @@ -311,6 +311,10 @@ Empty set (0.002 sec) 1 row in set (0.002 sec) ``` +## Statement truncation + +The `CREATE BINDING` statement can fail if it is used with `FROM HISTORY USING PLAN DIGEST` and if the statement is truncated because it is longer than [`tidb_stmt_summary_max_sql_length`](/system-variables.md#tidb_stmt_summary_max_sql_length-new-in-v40). If this happens it is recommended to increase `tidb_stmt_summary_max_sql_length`. + ## MySQL compatibility This statement is a TiDB extension to MySQL syntax. From 4036eca7286302d802d765966ca8283f57b1398b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dani=C3=ABl=20van=20Eeden?= Date: Tue, 23 Sep 2025 09:41:37 +0200 Subject: [PATCH 2/4] Update sql-statements/sql-statement-create-binding.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> --- sql-statements/sql-statement-create-binding.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sql-statements/sql-statement-create-binding.md b/sql-statements/sql-statement-create-binding.md index cd474b90e506d..eacac2ecf24f2 100644 --- a/sql-statements/sql-statement-create-binding.md +++ b/sql-statements/sql-statement-create-binding.md @@ -313,7 +313,7 @@ Empty set (0.002 sec) ## Statement truncation -The `CREATE BINDING` statement can fail if it is used with `FROM HISTORY USING PLAN DIGEST` and if the statement is truncated because it is longer than [`tidb_stmt_summary_max_sql_length`](/system-variables.md#tidb_stmt_summary_max_sql_length-new-in-v40). If this happens it is recommended to increase `tidb_stmt_summary_max_sql_length`. +If you use `CREATE BINDING` with `FROM HISTORY USING PLAN DIGEST`, the statement can fail if it is truncated for being longer than [`tidb_stmt_summary_max_sql_length`](/system-variables.md#tidb_stmt_summary_max_sql_length-new-in-v40). If this happens, increase `tidb_stmt_summary_max_sql_length`. ## MySQL compatibility From 08f0ca80d73a09a0e76ee96fe781f2b34eba0e72 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Dani=C3=ABl=20van=20Eeden?= Date: Wed, 24 Sep 2025 06:04:55 +0200 Subject: [PATCH 3/4] Update sql-statements/sql-statement-create-binding.md Co-authored-by: Grace Cai --- sql-statements/sql-statement-create-binding.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sql-statements/sql-statement-create-binding.md b/sql-statements/sql-statement-create-binding.md index eacac2ecf24f2..61c4b3b196963 100644 --- a/sql-statements/sql-statement-create-binding.md +++ b/sql-statements/sql-statement-create-binding.md @@ -313,7 +313,7 @@ Empty set (0.002 sec) ## Statement truncation -If you use `CREATE BINDING` with `FROM HISTORY USING PLAN DIGEST`, the statement can fail if it is truncated for being longer than [`tidb_stmt_summary_max_sql_length`](/system-variables.md#tidb_stmt_summary_max_sql_length-new-in-v40). If this happens, increase `tidb_stmt_summary_max_sql_length`. +When you use `CREATE BINDING ... FROM HISTORY USING PLAN DIGEST`, the binding can fail if the SQL statement stored in [statement summary tables](/statement-summary-tables.md) for that digest is truncated because it is longer than [`tidb_stmt_summary_max_sql_length`](/system-variables.md#tidb_stmt_summary_max_sql_length-new-in-v40). In this case, you need to increase `tidb_stmt_summary_max_sql_length`. ## MySQL compatibility From aa213217cc17c6c0f9cbe96078845d6c0c4a0b0c Mon Sep 17 00:00:00 2001 From: Grace Cai Date: Thu, 25 Sep 2025 10:16:50 +0800 Subject: [PATCH 4/4] minor wording updates --- sql-statements/sql-statement-create-binding.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sql-statements/sql-statement-create-binding.md b/sql-statements/sql-statement-create-binding.md index 61c4b3b196963..c34bfd9842ee5 100644 --- a/sql-statements/sql-statement-create-binding.md +++ b/sql-statements/sql-statement-create-binding.md @@ -311,7 +311,7 @@ Empty set (0.002 sec) 1 row in set (0.002 sec) ``` -## Statement truncation +## SQL statement truncation When you use `CREATE BINDING ... FROM HISTORY USING PLAN DIGEST`, the binding can fail if the SQL statement stored in [statement summary tables](/statement-summary-tables.md) for that digest is truncated because it is longer than [`tidb_stmt_summary_max_sql_length`](/system-variables.md#tidb_stmt_summary_max_sql_length-new-in-v40). In this case, you need to increase `tidb_stmt_summary_max_sql_length`.