Skip to content

Switch off archive_command on restored instance after success restoration #395

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

Closed
slothfk opened this issue Jun 9, 2021 · 5 comments
Closed

Comments

@slothfk
Copy link

slothfk commented Jun 9, 2021

Hi!
pg_barman comments string with archive_command in postgresql.conf on restored instance after recovery process successfully complete
can you make this feature by default behavior as pg_barman do this?

@gsmolk
Copy link
Contributor

gsmolk commented Jun 9, 2021

Hello!
It is almost impossible to do this deterministically, since archive_command can be defined in config file, that we have no knowledge about, or even be defined via command line parameter to postgres binary.
What problem are you trying to avoid exactly here?

@slothfk
Copy link
Author

slothfk commented Jun 9, 2021

What problem are you trying to avoid exactly here?

what is happened if i restore some instance in original environment where remote file server for backups is available and original instance is still work properly?

@gsmolk
Copy link
Contributor

gsmolk commented Jun 9, 2021

Same as with any restore: you will get an instance with new timeline and you will have a new timeline in your WAL archive.
This is correct behavior.

@slothfk
Copy link
Author

slothfk commented Jun 12, 2021

i start to understand now why we must use archive-push in archive_command directive

@gsmolk
Copy link
Contributor

gsmolk commented Jun 14, 2021

Can we close this issue or there are some questions left ?

@slothfk slothfk closed this as completed Jun 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants