We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
[This is more a feature idea or request]
Does not look good when cluster goes down when I need to revert a clster to an hour back.
Steps to reproduce: https://access.crunchydata.com/documentation/postgres-operator/latest/tutorials/backups-disaster-recovery/disaster-recovery#perform-an-in-place-point-in-time-recovery-pitr
Expected:
Reason: Clients will not notice the maintenance work.
There may be multiple strategies of doing PITR, so may worth to support multiple with ome flags.
The text was updated successfully, but these errors were encountered:
@vit-h, I have added a feature request to our backlog.
Sorry, something went wrong.
No branches or pull requests
[This is more a feature idea or request]
Does not look good when cluster goes down when I need to revert a clster to an hour back.
Steps to reproduce:
https://access.crunchydata.com/documentation/postgres-operator/latest/tutorials/backups-disaster-recovery/disaster-recovery#perform-an-in-place-point-in-time-recovery-pitr
Expected:
Reason: Clients will not notice the maintenance work.
There may be multiple strategies of doing PITR, so may worth to support multiple with ome flags.
The text was updated successfully, but these errors were encountered: