You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Checkout main
Apply migrations using flyway. We use the official flyway docker container.
Migration will fail as there are mixed transactional and non transactional migrations (due to the "concurrently" statements)
Resolving the above then fails because int_gpu_min referenced in the second statement doesn't exist (it was renamed in V11) and
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.
The text was updated successfully, but these errors were encountered:
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:
int_gpu_min
referenced in the second statement doesn't exist (it was renamed in V11) andi_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 ofi_layer_limit_pk_layer
but it would be good to know if we're missing something.The text was updated successfully, but these errors were encountered: