Jakub Jaruszewski
Jakub Jaruszewski
Not stale, please fix this
@hors Thanks, yes I'm aware, that's exactly what my issue is about. It's possible to deploy it without pgbouncer by using PostgresCluster (upstream one from PGO) CRD directly, but not...
TLDR it's the code at https://github.com/percona/percona-postgresql-operator/blob/v2.6.0/percona/controller/pgcluster/controller.go#L402 not utilizing https://github.com/percona/percona-postgresql-operator/blob/v2.6.0/internal/config/config.go#L103
I can also reproduce it on 2.60.3
The issue is that, if for any reason GC will fail, database and registry can be in desync (database state != registry storage state), subsequent GC won't fix it because...
Not stale, still a valid issue with no easy workaround
> I am facing the same issue with s3 used as storage, the GC doesn't delete blobs from s3 > > is there any workaround to clean up s3? Yes,...
> Hi @dmakeienko , > > * we don't recommend to run GC at storage of either delete the blobs manually. It would cause some inconsistency between storage and database...
You need to provide more info. How did you deploy it, where, what did you try?