-
Notifications
You must be signed in to change notification settings - Fork 0
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
Create process to migrate existing VegBank DB to new Postgres instance #29
Comments
@doulikecookiedough I created the |
@doulikecookiedough I added project info and labels to your ticket, and the milestone. |
Update: I am able to restore the comprehensive dump file provided by Nick to a Postgres 10.23 without any exceptions. However, restoring the records only dump file to Postgres 10.23 after executing
|
Update: I double checked all my commands, files... and noticed I was not using the data only dump file I had thought I was restoring from, but instead a manually created one. After using the correct data only dump file (and with the existing flyway migrations I put together in
|
Note: Work in progress can be found in branch A very exciting update - I was able to successfully load all the records from the data-only dump file by:
However, I am unable to apply the constraints afterwards. I think this is a promising direction, and will continue investigating.
|
Update: Successfully restored vegbank's data-only dump file into a vegbank db created via the flyway migration process. The changes/process can be found via Feature-29: Flyway Migration with Data-Only Dump File. This has been merged into Next Step: Kubernetes Depoyment and Set-up |
The restoration process described above can also be directly applied to a Postgres 12 (local server) or 16 (docker) instance without exceptions. |
This ticket has successfully migrated to newer postgres using Flyway. Moving the TODO items for building a helm chart to a separate issue (#33). This is now ready for review for the alpha1 release. |
Initial review and testing completed by @RWShelton, who is continuing work on the helm deployment in #33. Closing as flyway work is completed. |
To gather data and start working on the new RESTful API, we first need to get the existing postgres db/setup running so that we can investigate/poke-around.
To Do:
Subtasks deferred to #33:
The text was updated successfully, but these errors were encountered: