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
{{ message }}
This repository has been archived by the owner on Jan 18, 2024. It is now read-only.
What is missing?
Currently, there is no way to add options like db-include to the cluster restore process (pgbackrest_restore.sh). We want to create a whitelist of dbs to restore and whitelist of tables with certain databases to restore (this would use the tablespaces map option in pgbackrest).
Why do we need it?
Allows for a more official way to restore only the data we need in our clusters. Currently, we have a workaround where the post-init script drops unneeded dbs and tables but it causes us to restore all the data and then drop the stuff we don't want which is inefficient.
Anything else we need to know?:
Thank you!
The text was updated successfully, but these errors were encountered:
In general there is no way to mount custom files seemingly either. Meaning you can't create a separate script and point to it despite being able to configure what script the restore command points at.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What is missing?
Currently, there is no way to add options like db-include to the cluster restore process (pgbackrest_restore.sh). We want to create a whitelist of dbs to restore and whitelist of tables with certain databases to restore (this would use the tablespaces map option in pgbackrest).
Why do we need it?
Allows for a more official way to restore only the data we need in our clusters. Currently, we have a workaround where the post-init script drops unneeded dbs and tables but it causes us to restore all the data and then drop the stuff we don't want which is inefficient.
Anything else we need to know?:
Thank you!
The text was updated successfully, but these errors were encountered: