From: stevenchang1213 <stevenchang1213@gmail.com>
To: Robin LUCBERNET <rlucbernet@maltem.com>
To: Lazaro Garcia <lazaro3487@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: How do you manage cluster replication and failover ?
Date: Sat, 08 Apr 2017 07:43:45 +0800
Message-ID: <58e82436.4166630a.4ceb5.97b1@mx.google.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
you are talking about product features. I suggest u study by urself. None will confirm u anything here. All is free charge here , you should think about what it means.
steven
-------- 原始訊息 --------自： Robin LUCBERNET <rlucbernet@maltem.com> 日期： 2017/4/7 23:33 (GMT+08:00) 至： Lazaro Garcia <lazaro3487@gmail.com>, pgsql-admin@postgresql.org 主旨： Re: [ADMIN] How do you manage cluster replication and failover ?
<!-- P {margin-top:0;margin-bottom:0;} -->
Hey, thanks for your feedbacks.
I do not know about Patroni. I will have a look at it.
Could someone confirm me that all features of pgpool (connection pooling + automatic failover) can be achieve using pgbouncer (connection pooling) + repmgr (automatic failover) ? Is it not overkill to user repmgr + pgpool ? Am I missing something ?
Robin.
De : Lazaro Garcia <lazaro3487@gmail.com>
Envoyé : vendredi 7 avril 2017 15:26:41
À : Robin LUCBERNET; pgsql-admin@postgresql.org
Objet : RE: [ADMIN] How do you manage cluster replication and failover ?
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 ?
Robin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: stevenchang1213@gmail.com, rlucbernet@maltem.com, lazaro3487@gmail.com
Subject: Re: How do you manage cluster replication and failover ?
In-Reply-To: <58e82436.4166630a.4ceb5.97b1@mx.google.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox