You can use repmgr because it performs automatic failover, promotes a master mores closer to replica and follows other slaves to new master.
Then pgpool detects the new master promoted by repmgr.
Regards.
De: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] En nombre de Robin LUCBERNET Enviado el: jueves, 6 de abril de 2017 05:18 a. m. Para: pgsql-admin@postgresql.org Asunto: [ADMIN] How do you manage cluster replication and failover ?
Hello,
We are currently trying to setup a multi hosts databases cluster with goals: * replication (no data-loss is "required", replication timing do not needs to be instant) * failover * load-balancing (bonus)
We tried: * synchronious replication (pgpool replication mode) + load-balancing (pgpool) : very interesing as we can theorically failover on any node at any moment. But even after several configuraation tweeks, we never succeed getting good write performance. * asynchronious replication (postgres 9.6 streaming replication) : good write performance, good replication timings (< 1 second for small transactions). We could loadbalance select requests using pgpool.
How do you manage your postgresql clusters ? Do you use pgpool ? pgbouncer ? other ? How do you manage to single access point ? usign pgpool ? pgbouncer ? Do you use streaming replication ? WAL archiving ? How do you handle to automatic failover ?
