From: Joseph Mays <mays@win.net>
To: pgsql-admin@postgresql.org
Subject: Pgpool-II, pgcluster, or pgbouncer?
Date: Thu, 17 Jul 2014 12:53:49 -0400
Message-ID: <52E4C0ED4C424CF5BFA534D92A8534F9@Gantry> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
I have a site that has a postgres database server. 24 hour availability is pretty critical to them, so I want to turn it into a redundant cluster for high availability. I currently have a streaming backup server, but we want to be able to make either server capable of accepting writes in the case one fails. The problem with streaming backup is that we can promote the backup when the master fails, but when the master comes backup you basically have to rebuild the entire database and reconfigure postgres on it to either make it the master or make it into a new streaming backup. We want something that’s much more dynamic, so writes can go either direction in the event of one or the failing, and so that things will automatically resync when a failed server in the cluster comes back online.
Given these goals – pgpool-II, pgcluster, pgbouncer? Some other tool that I haven’t even considered?
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: mays@win.net
Subject: Re: Pgpool-II, pgcluster, or pgbouncer?
In-Reply-To: <52E4C0ED4C424CF5BFA534D92A8534F9@Gantry>
* 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