-
Notifications
You must be signed in to change notification settings - Fork 4.1k
sql/schemachanger: prerequisites to setting schema changer "on" by default #59788
Copy link
Copy link
Closed
Labels
C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Description
- GC dropped indexes.
- Disable the new schema changer for computed columns. See sql: enable adding columns which are not written to the current primary index #59149.
- Ensure that only one "new" schema change can be running on a table at a time, by restarting transactions that would initiate new schema changes (either from the old or the new schema changer) until there are no preexisting mutations on the table.
- Support reverting schema changes on failure or job cancelation.
- Properly checkpoint and read job progress for the index backfill.
Epic: CRDB-2356
Jira issue: CRDB-3234
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)SQL Foundations Team (formerly SQL Schema + SQL Sessions)