-
Notifications
You must be signed in to change notification settings - Fork 87
Issue 280 #295
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
Conversation
…wing to replace already existing cluster with different system ID. Also more conservative approach is enforced towards remapped tablespaces and external directories, now it is forbidden to reuse already existing content in remapped tablespace directory. The already existing content of remapped tablespace can be replaced if "--force" flag is used.
…_missing_or_corrupted_tablespace_map
When used with <link linkend="pbk-incremental-restore">incremental restore</link> this flag | ||
allows to replace already existing PGDATA with different system ID. In case of tablespaces, | ||
remapped via <literal>--tablespace-mapping</literal> option into not empty directories, | ||
the old content of such directories will be deleted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In case tablespaces are remapped into non-empty directories, the content of such directories will be deleted.
And what about external-dirs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For them nothing is changed, not empty destination directory is still an error condition, but that is the default behavior, so I don`t think that we should specially mention it.
Merged manually |
Expand
--force
flag.#280