Skip to content
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

Separate DDL operations from DML (backfills) on migration start #289

Merged
merged 2 commits into from
Feb 29, 2024

Conversation

andrew-farries
Copy link
Collaborator

@andrew-farries andrew-farries commented Feb 28, 2024

Separate the DDL operations required during migration start from the DML operations (backfills). Complete all DDL steps before starting DML.

Each Start operation returns the name of the table that requires backfill, if any. After all operations have started, backfills are run on each table that requires one.

Separating DDL and DML during migration start like this will allow for setting Postgres options that should apply only for the DDL phase of migration start (as in #290).

Return the table that needs backfill, if any.
Collect all the tables that require backfill and backfill them once the
DDL operations on `Start` have completed.
Copy link
Member

@exekias exekias left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚀 love to see this! it will actually speed up some migrations and provide better control & info over the migration progress! I left a few comments

@andrew-farries andrew-farries merged commit 0746ba6 into main Feb 29, 2024
42 checks passed
@andrew-farries andrew-farries deleted the backfill-after-ddl-operations branch February 29, 2024 06:39
andrew-farries added a commit that referenced this pull request Mar 1, 2024
…column in a backfill. (#298)

Add a test to ensure that new columns can't be used as the identity for
a backfill, even if they satisfy the conditions for an identity column.

A newly added `NOT NULL` and `UNIQUE` column could in theory be used as
the identity column for a backfill. However, it shouldn't be used as the
identity column fora backfill because it's a newly added column whose
temporary column will be full of NULLs for any existing rows in the
table.

Currently the column won't be selected as an identity for backfills
because the nullability and uniqueness for new column are not populated
when adding it to the virtual schema in the add_column operation:


https://github.com/xataio/pgroll/blob/c08ef7065cdbce965110e64f58e66eddf605eaee/pkg/migrations/op_add_column.go#L61-L63

Following on from the discussion here:
#289 (comment)
andrew-farries added a commit that referenced this pull request Oct 10, 2024
Progress updates showing how many rows have been backfilled during
migration start were added in #139.

Progress updates were then broken in
#289.

Fix the progress updates to restore the intended behaviour from #139 and
add a test to ensure that callbacks are invoked during migration start.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants