Benjamin Blattberg

I'm not sure what the issue here is. If you're still experiencing trouble with this, please describe what you're trying to do and how it is not working.

I haven't seen this behavior before. Can you give more info about (a) your environment (including kubernetes version) and (b) the particular postgres cluster (such as the yaml)? ETA: Wait,...

Closing this as near-enough a duplicate of #59 + I've captured it in our backlog

Could you (a) rebase off `devel` (b) PR this to merge into `devel` (c) and add resources to the manager-upgrade.yaml as well? (thanks for pointing that out @tkp75 )

Tested and made some slight changes (oh and squashed into one commit), thanks for the PR -- can you deploy with Helm with these changes?

(a) Are you still experiencing this problem? If so, what do the pvc and pv look like for a pod created by the postgres-operator? (b) Also are you able to...

OK, sorry, I went through a few things and I keep editing this as more info comes in, and here's what I've got: I am able to replicate this issue...

Hello, just to double-check something in the logs: do you have multiple postgresclusters named `eportaldb`? And are you attempting restores on multiple clusters at the same time?

Hi @jelmer, First, thanks for this. Second, I'm hoping to merge [the dependency update](https://github.com/CrunchyData/postgres-operator/pull/3362) sometime this week, which includes changes like a generic logging update, the Handler=>ProbeHandler change, and the...

Hey @jelmer thanks, my branch was still in-progress when you rebased -- can you maybe rebase off `master` now instead?