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

Fixes #1393

Merged
merged 4 commits into from
Jan 23, 2024
Merged

Fixes #1393

merged 4 commits into from
Jan 23, 2024

Conversation

midenok
Copy link
Collaborator

@midenok midenok commented Jan 22, 2024

No description provided.

STRICT_TRANS_TABLES fails empty values in enum fields.
This happens because InnoDB cannot drop table if some DML works with
foreign table referencing it (even under FOREIGN_KEY_CHECKS=0).

For --overwrite-tables we don't start DML until all table creation
processed. But since this is not 100% success guarantee as a second
measure we implement retry mechanism with retry_queue which collects
failed tables and retries them upon JOB_SHUTDOWN.

--retry-count sets maximum number of such retries (default 10).

--overwrite-unsafe cancels all the above and works like before the
patch.

There also wrong semantics used in overwrite_table() for m_query() for
TRUNCATE and DELETE. These are fixed in this commit.
--max-threads-per-table-hard removed as it does nothing more than
--max-threads-per-table does.

--threads value is autodetected to the number of CPUs by default.

--max-threads-per-table by default is set to the value of --threads.
Leftover fix in test_case_stream
@davidducos davidducos merged commit 151f5eb into mydumper:master Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants