Skip to content
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

DM internal tables does not have PK so can't work with sql_require_primary_key=ON #11786

Open
lance6716 opened this issue Nov 22, 2024 · 0 comments

Comments

@lance6716
Copy link
Contributor

lance6716 commented Nov 22, 2024

What did you do?

turn on sql_require_primary_key and run DM

What did you expect to see?

no error

What did you see instead?

Unable to create or change a table without a primary key, when the system variable 'sql_require_primary_key' is set. Add a primary key to the table or unset this variable to avoid this message. Note that tables without a primary key can cause performance problems in row-based replication, so please consult your DBA before changing this setting.

Versions of the cluster

all version

current status of DM cluster (execute query-status <task-name> in dmctl)

(paste current status of DM cluster here)

ref pingcap/tidb#57479

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants