Open
Description
We should look into doing something like https://www.2ndquadrant.com/en/blog/add-new-table-column-default-value-postgresql-11/:
In a new feature I worked on and committed, the default value is just stored in the catalog and used where needed in rows existing at the time the change was made. New rows, and new versions of existing rows, are written with the default value in place, as happens now.
We might consider allowing users to specify when to issue the rest of the backfill job so that they can avoid periods of heavy cluster traffic
We need to be sure to consider how this approach might affect AOST (time-travel) queries that read historical data.
https://cockroachlabs.slack.com/archives/C04N0AS14CT/p1716479612947039
Jira issue: CRDB-40160