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

Issue with v18 migrations #1354

Open
grimjak opened this issue Apr 12, 2024 · 0 comments
Open

Issue with v18 migrations #1354

grimjak opened this issue Apr 12, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@grimjak
Copy link

grimjak commented Apr 12, 2024

Describe the bug
Applying the V18 migrations to add additional indices fails on an up to date install

To Reproduce
Steps to reproduce the behavior:

  1. Checkout main
  2. Apply migrations using flyway. We use the official flyway docker container.
  3. Migration will fail as there are mixed transactional and non transactional migrations (due to the "concurrently" statements)
  4. Resolving the above then fails because int_gpu_min referenced in the second statement doesn't exist (it was renamed in V11) and
  5. i_layer_limit_pk_layer already exists (created in V12)

Expected behavior
Migrations to be applied succesfully

Screenshots
If applicable, add screenshots to help explain your problem.

Version Number
Version 0.22 from main

Additional context
We worked around this by removing concurrently from the create index statements and commenting out the creation of i_layer_limit_pk_layer but it would be good to know if we're missing something.

@grimjak grimjak added the bug Something isn't working label Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant