-
Notifications
You must be signed in to change notification settings - Fork 93
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
Problems with migrations for 0.12.0 #688
Comments
@hypnoglow hmm, there wasn't a |
@bgentry You're right. But your migration guide suggests to run the following query to create it manually, because it is used in the index: ALTER TABLE river_job ADD COLUMN unique_states BIT(8);
CREATE UNIQUE INDEX CONCURRENTLY river_job_unique_idx ON river_job (unique_key)
WHERE unique_key IS NOT NULL
AND unique_states IS NOT NULL
AND river_job_state_in_bitmask(unique_states, state); Then the guide recommends running river migrator, and so ALTER is executed second time. |
@hypnoglow Ah yes that's quite right. We'll get a fix shipped for this immediately. Thanks for reporting! |
As described in #688, if a user has followed changelog instructions to create the new index concurrently, they will encounter an error as they try to run the 006 migration to finalize it. Here, tolerate the column already existing to fix the problem. An existing index is already tolerated. Fixes #688.
As described in #688, if a user has followed changelog instructions to create the new index concurrently, they will encounter an error as they try to run the 006 migration to finalize it. Here, tolerate the column already existing to fix the problem. An existing index is already tolerated. Fixes #688.
As described in #688, if a user has followed changelog instructions to create the new index concurrently, they will encounter an error as they try to run the 006 migration to finalize it. Here, tolerate the column already existing to fix the problem. An existing index is already tolerated. Fixes #688.
As described in #688, if a user has followed changelog instructions to create the new index concurrently, they will encounter an error as they try to run the 006 migration to finalize it. Here, tolerate the column already existing to fix the problem. An existing index is already tolerated. Fixes #688.
Thank you 💙 |
…#690) As described in riverqueue#688, if a user has followed changelog instructions to create the new index concurrently, they will encounter an error as they try to run the 006 migration to finalize it. Here, tolerate the column already existing to fix the problem. An existing index is already tolerated. Fixes riverqueue#688.
Just FYI In release descripion https://github.com/riverqueue/river/releases/tag/v0.14.3 PR links are mixed up with each other. |
@hypnoglow thanks, fixed the GitHub release and will tweak the changelog too 🙏 |
Inverts links on #690 and #691 which currently point to each others pull requests instead of their own, as reported in [1]. [1] #688 (comment)
CHANGELOG upgrade guide recommends running index migration manually for large tables. After that, "normal" river migration should be run to finalize the process.
The problem is that the existing index is tolerated, but the existing column is not, which results in the following error:
The text was updated successfully, but these errors were encountered: