syn2mas: reconstruction of indices and constraints is not atomic #3940

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.

Sign up for GitHub

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

Jump to bottom

Open

reivilibre opened this issue Feb 2, 2025 · 0 comments

Labels

Contributor

reivilibre commented Feb 2, 2025

If syn2mas is interrupted whilst rebuilding indices and constraints, you end up with some of them left on the database.

When you next run syn2mas, it truncates all the tables but does not remove those indices/constraints.

I also suspect if you left it run through to the end at that point, that it will try to double-create them.

Solution suggestion:

when recreating an index, delete the row from the restore table (in the same transaction!)
when restarting a migration, it should drop indices again and append the definitions to the restore table, so that it works as it did before.

reivilibre added the A-Migration label

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