-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
sql: cannot perform other schema changes concurrently with alter column type #47137
Comments
#49351 covers this |
re-opening, since this is referenced here: cockroach/pkg/sql/alter_column_type.go Line 220 in 4b8a9c7
|
I feel like this isn't really about wanting the operations to occur concurrently, it's about wanting them to be ordered. |
ref https://github.com/cockroachdb/django-cockroachdb/blob/5.1/README.md cc @timgraham is there a possibility to await the change / make the query block until the change finishes? |
I thought the asynchronous part was fixed such that the statement doesn’t now return until the alter is complete. That comment may be stale. Is it something you see on later cockroach versions? |
we are in research phase, and this looked like a blocker if we want to move to cockroachdb. can this issue be closed and the django-cockroachdb README amended? |
I believe the stable CockroachDB docs still state this restriction:
|
@rafiss is it true? My recollection is that the the alter job waits on the job it creates and has for years. |
For context, we saw an intermittent failure in Django with CockroachDB 21.1 (#65691). Since then the test has been on the skip list. |
hi all 👋 did you happen to discuss this internally in the meantime? this would be a hard blocker to migrate our django project over from vanilla postgres |
Currently, ALTER COLUMN TYPE cannot be performed concurrently with other schema changes.
For example you cannot add a column while an alter column type is occuring, you cannot alter primary key while alter column type is occuring.
Jira issue: CRDB-5036
Epic CRDB-25314
The text was updated successfully, but these errors were encountered: