pg_auto_failover icon indicating copy to clipboard operation
pg_auto_failover copied to clipboard

Postgres extension and service for automated failover and high-availability

Results 116 pg_auto_failover issues
Sort by recently updated
recently updated
newest added

Hello, we are experiencing a memory leak in the combination of pg_auto_failover v2.0 and PostgreSQL v15. The pg_autoctl: node active process is successively taking up all the memory of the...

bug
good first issue

# Release TODO List - [x] Add a `CHANGELOG` entry summarizing meaningful changes, starting with the output of the command `git log --oneline $(git describe --tags --abbrev=0 --match "v[0-9]*" HEAD)^..`...

release_checklist

Hi @dimitri @DimCitus , 2.0 fails to build against v16. v16 is due next week. Can you please take a look? Thanks! Regards, Devrim

Good afternoon. The other day during testing, I encountered the problem of the switchover/failover hanging in the report_lsn standby status. Switchover/failover could not be completed due to the unavailability of...

Hi Folks, I play around a bit with pg_auto_failover and try to set the `candidate-priority` for the node `db-3` but I always get an error, see below. ``` postgres@db-monitor:~$ pg_autoctl...

The main point here is to allow faster builds and regression testing. So instead of building container image with pgaf source code included we build more specialized images without source...

What's the correct way to initialize a an already existing primary server? The [install page](https://pg-auto-failover.readthedocs.io/en/main/install.html#avoiding-the-default-postgres-service) suggests to avoid automated creation of a Postgres data directory. The [pg_autoctl create page](https://pg-auto-failover.readthedocs.io/en/main/ref/pg_autoctl_create_postgres.html#description) explains...

good first issue
docs

Hi, Thank you developers for your work! Now about the problem :) There are 3 DCs: - 2 of them have nodes (primary and secondary) - in the 3rd DC...

bug
good first issue

Salut Dimitri, I try to raise twice ( on a healthy cluster) pg_autoctl enable maintenance, return code is 0 (event if the second time I have the message Node already...

bug
good first issue

**Setup:** We are running postgres server in containers on Kubernetes cluster. **Issue:** While looking at the pg_auto_failover debug logs, found an interesting log snippet related to pgtuning: ``` 17:15:05 105...

bug
good first issue