Skip to content

cloud: add new limitations on TiDB serverless for 7.1 #15645

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: release-7.1
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions system-variables.md
Original file line number Diff line number Diff line change
Expand Up @@ -4150,6 +4150,10 @@ SHOW WARNINGS;

### tidb_replica_read <span class="version-mark">New in v4.0</span>

>**Note:**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's nice to have this note as cross reference.

Unfortunately, all the rest variables and statements did not have this. We should add them all or none.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed.

Copy link
Collaborator

@qiancai qiancai Feb 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you search TiDB Serverless on https://docs.pingcap.com/tidb/dev/system-variables, you'll find there are more than 60 instances that indicate the TiDB Serverless support info.

For example:
image

Therefore, it looks OK to add the support info for this variable too.

>
>This variable is not supported on [TiDB Serverless](https://docs.pingcap.com/tidbcloud/select-cluster-tier#tidb-serverless).

- Scope: SESSION | GLOBAL
- Persists to cluster: Yes
- Type: Enumeration
Expand Down
15 changes: 14 additions & 1 deletion tidb-cloud/limited-sql-features.md
Original file line number Diff line number Diff line change
Expand Up @@ -223,12 +223,23 @@ TiDB Cloud works with almost all workloads that TiDB supports, but there are som
| `validate_password.policy` | No limitation | Can only be `MEDIUM` or `STRONG` [^10] |
| `validate_password.special_char_count` | No limitation | At least `1` [^10] |
| `wait_timeout` | No limitation | Read-only [^11] |
| `tidb_replica_read` | No limitation | Read-only [^14] |

## Optimizer Hint

| Hint | TiDB Dedicated | TiDB Serverless |
|:-|:-|:-|
| `RESOURCE_GROUP()` | No limitation | Not supported |
| `RESOURCE_GROUP()` | No limitation | Not supported |
| `MEMORY_QUOTA()` | No limitation | Not supported |
| `MAX_EXECUTION_TIME()` | No limitation | Not supported |
| `READ_CONSISTENT_REPLICA()` | No limitation | Not supported [^14] |

[^1]: Configuring data placement is not supported on TiDB Serverless.

[^2]: Configuring resource groups is not supported on TiDB Serverless.

[^3]: To perform [Back up and Restore](/tidb-cloud/backup-and-restore-serverless.md) operations on TiDB Serverless, you can use the TiDB Cloud console instead.
[^3]: To perform [Back up and Restore](/tidb-cloud/backup-and-restore-serverless.md) operations on TiDB Serverless, you can use the TiDB Cloud console instead.

[^4]: The feature is unavailable in [Security Enhanced Mode (SEM)](/system-variables.md#tidb_enable_enhanced_security).

Expand All @@ -249,3 +260,5 @@ TiDB Cloud works with almost all workloads that TiDB supports, but there are som
[^12]: Customizing cache size using [`AUTO_ID_CACHE`](/auto-increment.md#cache-size-control) is temporarily unavailable on TiDB Serverless.

[^13]: Not supported. Enabling `require_secure_transport` for TiDB Dedicated clusters will result in SQL client connection failures.

[^14]: `tidb_replica_read` only supports `leader` on TiDB Serverless.