release-25.4: workload/schemachange: don't predict deps on DROP COLUMN#170010
release-25.4: workload/schemachange: don't predict deps on DROP COLUMN#170010spilchen wants to merge 1 commit intocockroachdb:release-25.4from
Conversation
The schemachange workload tried to predict precisely when DROP COLUMN would fail with DependentObjectsStillExist. Keeping that prediction in sync with the schema changer has been a steady source of flakes. Move the error to potentialExecErrors so it is permitted but not required, and delete the dependency-detection helpers that fed the old prediction. Resolves cockroachdb#168658 Release note: None Epic: none
|
Merging to
After your PR is submitted to the merge queue, this comment will be automatically updated with its status. If the PR fails, failure details will also be posted here |
|
Thanks for opening a backport. Before merging, please confirm that it falls into one of the following categories (select one):
Add a brief release justification to the PR description explaining your selection. Also, confirm that the change does not break backward compatibility and complies with all aspects of the backport policy. All backports must be reviewed by the TL and EM for the owning area. |
|
Detected infrastructure failure (matched: self-hosted runner lost communication with the server). Automatically rerunning failed jobs. (run link) |
Backport 1/1 commits from #169328.
/cc @cockroachdb/release
The schemachange workload tried to predict precisely when DROP COLUMN would fail with DependentObjectsStillExist. Keeping that prediction in sync with the schema changer has been a steady source of flakes.
Move the error to potentialExecErrors so it is permitted but not required, and delete the dependency-detection helpers that fed the old prediction.
Resolves #168658
Release note: None
Epic: none
Release justification: test only fix