-
When you try to add one replica beyond `max_wal_senders` it panics on boot.
```sh
P2023-03-20T22:09:14Z app[21781770c63089] den [info]Provisioning standby
2023-03-20T22:09:15Z app[21781770c63089] d…
-
In past we had run 3 PSQL instances on one server. That's why we needed a differentation of repmgr table. They were called repmgr.claas, repmgr.linde, repmgr.proemion,
In a single PSQL instance env…
-
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 - however if i run crossch…
-
Hi,
I'm playing with AlloyDB Omni, which is a standard PGSQL wrapped in a container and packed with some GCP (Google) steroids. Everything is working well, I was able to build a simple config with …
-
Hello, during my simulation of host failover, I stopped the master host's PostgreSQL instance, and the standby node successfully switched to become the new master node. However, when I restarted the …
-
Even if the connection_check_type setting in repmgr is changed to query, the self-check method is still performed using PQping.
Is there a way to change all connection check methods to a method othe…
-
### Name and Version
bitnami/postgres-repmgr:16.0.0
### What architecture are you using?
None
### What steps will reproduce the bug?
1. Follow the guide "Using a Docker Compose file" on "https://…
-
docker.io/gitea/gitea:1.22.0-rootless
docker.io/bitnami/pgpool:4.5.2-debian-12-r0
docker.io/bitnami/postgresql-repmgr:16.3.0-debian-12-r9
docker.io/bitnami/redis-cluster:7.2.5-debian-12-r0
-
According to the [docs](https://www.pgpool.net/docs/latest/en/html/runtime-config-failover.html) `follow_primary_command` specifies a user command to run after failover on the primary node failover. T…
-
There is an annoying issue with barman taking backups from instances that have a separate conf directory where config files live in instead of in the data directory.
Although barman takes a fine ba…
gplv2 updated
3 months ago