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

When creating a monitor you need to manually set password for `autoctl_node` user using ``` // postgres needs to run psql postgres://localhost/pg_auto_failover -c "alter user autoctl_node password 'h4ckm3'" ``` When...

Use environment variables rather than very long command lines where it makes sense, making it easier to see that we're doing the same thing in the three Postgres nodes.

Size: S

Hey, something that came up in our discussions is whether pg_auto_failover could handle configuration of delayed replicas. With the current version it should be possible to achieve this by using...

enhancement

This is a work in progress. The idea is to add support for Disaster Recovery in pg_auto_failover. This is not ready for review, it's mostly just a remote backup of...

enhancement

Add an interesting story where we migrate from one region to another thanks to a short list of pg_auto_failover commands. This time this happens in Europe.

docs

Hello, I have a 3 node setup, 1 primary, and 2 secondaries. The primary node's server went down and another node got promoted to primary just fine. I tried a...

When we enable pg_auto_failover for an existing postgres cluster, the pg_hba.conf on standby hasn't the following 2 rules compared with that of the primary. ``` host(ssl) all "pgautofailover_monitor" _host_ trust...

Please provide a parameter where we could specify a command for backup, aim is to use our favorite (defaut will be pg_basebackup, same behaviour as of today). We think it...

Hello, pg_autoctl create node breaks because of passwordcheck contrib module (it seems passwords for users created by pg_autoctl are the same as user name). For security reasons we need this...

All of the steps in the pg-auto-failover installation process should be done using postgres user. Otherwise when running the nodes there are some permission errors. We should mention postgres user...