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

Optimize DELETE performance for range deletion #1055

Open
overvenus opened this issue Jun 13, 2021 · 0 comments
Open

Optimize DELETE performance for range deletion #1055

overvenus opened this issue Jun 13, 2021 · 0 comments
Labels
feature-request This issue is a feature request

Comments

@overvenus
Copy link
Member

Bug Report

Please answer these questions before submitting your issue. Thanks!

  1. What did you do?
    If possible, provide a recipe for reproducing the error.

Range deletion is being translated into multiple single deletion SQL in the drainer. The overhead could be huge, and they slow down the synchronization.

  1. What did you expect to see?

For this case, the drainer should be able to understand range deletion or able to optimize multiple single deletion.

  1. What did you see instead?

  2. Please provide the relate downstream type and version of drainer.
    (run drainer -V in terminal to get drainer's version)

@overvenus overvenus added the feature-request This issue is a feature request label Jun 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request This issue is a feature request
Projects
None yet
Development

No branches or pull requests

1 participant