seadba

Results 3 issues of seadba

following the instructions in quick start - it appears the cluster has been created ``` NAME READY STATUS RESTARTS AGE pgo-5858b776c6-8klw4 1/1 Running 0 105s kubectl get pod --namespace=postgres-operator NAME...

we have an issue with offline replicas - i have an orphaned stolon replication slot in primary - pg_wal needs to be trimmed - can i safely drop the stolon_...

i have a v11 cluster on a non-default port 5443 - i have passwordless authentication set up and repgmr config works - nodes are registered and standby cloned and recovering...