Benjamin Blattberg

Hello, we're discussing possible solutions to overly long names (and labels), as this is not isolated to cronjob names. In the meantime, we're truncating our cronjob name by dropping the...

(Adding the `backlog` label just to indicate that we have this feature in our backlog and are tracking it.)

The https://github.com/CrunchyData/postgres-operator/pull/3400 should resolve these issues and is planned to be available in the next release, but not currently planned to be backpatched to v4. As noted, the manual fix...

Thanks for the PR -- approved and merged! Hope that helps debug init sql issues.

Hi @hstefan, could you add some info about what platform, system, etc. you're using for this? - Platform: (`Kubernetes`, `OpenShift`, `Rancher`, `GKE`, `EKS`, `AKS` etc.) - Platform Version: (e.g. `1.20.3`,...

Hello, Because (a) I cannot replicate this behavior and (b) the pgbackrest code looks like it should remove the storage _path_, not just the contents, this seems like unexpected behavior,...

Hmmm, that's curious, but just to make sure I understand, you list two PGO image versions (`ubi8-5.1.0-0` and `ubi8-5.0.5-0`) and two PG version (`14` and `13`) -- was there any...

Since that workaround works for now and we have an issue opened in pgbackrest, I'll close this issue now, but feel free to reopen if there's more here to discuss.

Just writing to let you know that we have this issue in our backlog as it is a fairly common feature request.

@dberardo-com That blog post is a little old -- if you're starting fresh now, you probably want to install PGO v5 (5.2.0 is the latest). And for that, we have...