AAP-16926 Delete unpartitioned tables in a separate transaction #14572
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
My prior merge #14055 broke cleanup jobs, and this is me trying to fix that.
The issue is pretty high level:
https://stackoverflow.com/questions/12838111/django-db-migrations-cannot-alter-table-because-it-has-pending-trigger-events
And what we saw were errors of this type:
That error is really hard to make sense of. Within my process of troubleshooting this issue, I tried to manually drop all the constraints on the unpartitioned tables before dropping them. That led to this interesting error:
That starts to jive really well with the above statement that "you must not update the table and then alter the table schema".
ISSUE TYPE
COMPONENT NAME