-
Notifications
You must be signed in to change notification settings - Fork 274
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
Disadvantages of backup and recovery #1277
Comments
I believe you would be better served with: ALTER EXTENSION pgml UPDATE; Dropping the extension drops all trained models, because those tables are owned by the extension. |
Okay, thanks, so the application scenario of pgml backup and recovery applies to extension upgrades. Is my understanding correct? |
I tried to use dump_all and load_all for backup and recovery, but between backup and recovery I tried to uninstall and reinstall the extension, which made the new train impossible. It seems that the new environment did not add code logic to judge the projects table. Whether the same id already exists in .
There is already data in the table about projects、models....
Is the result of my usage considered a bug?
The text was updated successfully, but these errors were encountered: