-
Notifications
You must be signed in to change notification settings - Fork 4.1k
sql: incremental index backfills #70426
Copy link
Copy link
Closed
Labels
A-disaster-recoveryC-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-disaster-recovery
Description
As described in #69380, once #70422 lands index backfills should be incremental. I.e. they should first build the index based on existing data, and then do another backfill to update the index with any writes that have happened in the meanwhile, and so on.
Related to #63741.
Epic: CRDB-10258
Jira issue: CRDB-10069
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-disaster-recoveryC-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-disaster-recovery