-
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
back_up_postgresql should create separate dump files for each database #2
Comments
So basically I want sql files for the roles/tablespaces, and then a dump file for each DB. Hmm. pg_dumpall takes |
Perhaps we should also make it possible for the user to specify a desired dump format? Some of them sound quite interesting (directory with a file per table, or a tar of the above). |
Uh, it should be documented that back_up_postgresql only does it for the default cluster (you can have multiple clusters, running different PostgreSQL versions, and OS upgrades often leave it that way!) |
I've changed my mind on dump formats:
SQL is portable; efficient binary formats from random PostgreSQL versions are apparently not. (This was a dump create with pg_dump -Fc on 9.4, pg_restore was version 10.5.) |
back_up_postgresql now uses pg_dumpall and dumps everything into a single file.
I'd prefer to have separate dump files for each database.
The text was updated successfully, but these errors were encountered: