andrewlecuyer

I see that you are running a very old version of Docker - v1.13.1 was released on 2017-02-08. It therefore looks like you are missing countless updates/patches across your OS,...

@cdaller thank you for the detailed issue submission. As you are seeing, PGO is currently opinionated about the stanza for any repos it manages, and will therefore always set the...

@anonymouse-jj thank you for using PGO! Just noting that we have an enhancement in our backlog to make Disaster Recovery features (e.g. backups) optional for non-production use cases.

We are not seeing any functional impact or issue per @dsessler7's response above. More specifically, PGO appears to be reconciling repo changes as designed. Therefore, proceeding with closing.

Thanks for all of the feedback and input on this one. Just noting that a story has been added to the PGO backlog for consideration in a future release.

@trevor-primer it should be possible to modify your repos after cluster creation. Can you provide a copy of your operator logs after attempting to modify the repos? Any logs from...

@trevor-primer just following-up to see if you're able to provide the additional details, logs, etc. requested in my last message. Thanks!

Closing as unable to reproduce.

@kyle-rf I have been unable to reproduce the behavior you are seeing. Specifically, when I follow the steps you provided (i.e. to upgrade from v4.6.2 to v4.7.4), I see the...

Just noting that this has been fixed in Patroni 2.1.4, which will be included in the next release of PGO.