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

Hi Running several clusters within a single monitor. Try to move existing clusters from one monitor to another monitor in third site. Some succeeds, but in the case of nodeid...

enhancement
user experience

Using the environment variable allows to omit the replication password from the logs, though messes with next connection attempts. We should either call unsetenv() once the pg_basebackup command has finished,...

bug
Size: S

We don't actually need to have a password for this user, given that the monitor doesn't authenticate when doing health checks. Not having a password to manage also makes it...

bug
Size: S

pg_auto_failover version 1.5.2 During first initialization of cluster (monitor + 2 postgres nodes) we discovered that secondary postgres node uses the replication password when connecting to the monitor after initial...

bug
Size: S

To implement HA we need automated failover and also Disaster Recovery for the availability of the data. With Postgres that means archiving. Then, archiving intersects with auto-failover in multiple ways,...

enhancement
user experience
Size:L

When a node is ongoing maintenance, the operator can use our maintenance state to avoid our automation to continue driving the node. We're asked to get pg_auto_failover out of the...

bug
enhancement
user experience
Size:M

Consider the following state we encountered today during testing: ``` Name | Node | Host:Port | LSN | Connection | Current State | Assigned State --------+-------+--------------+------------+--------------+---------------------+-------------------- db002-2 | 4 |...

bug
Size:M

If you've put your certificates and keys at the default locations inside the nodes' data directories (and pointed to them with `pg_autoctl enable ssl`), then the primary's cert and key...

bug
good first issue

The following code that we use a lot is undefined behavior: ```c paramValues[1] = intToString(index).strValue; ``` Instead it should be: ```c IntString indexStr = intToString(index); paramValues[1] = indexStr.strValue; ``` With...

bug
enhancement
Size:M

The existing PGDATA might have come from a former primary that's not in the new timeline and where pg_rewind is needed to go before the fork LSN. Also, it could...

bug
Size:M