From: Joseph Mays <mays@win.net>
To: pgsql-admin@postgresql.org
Subject: PG server clustering
Date: Thu, 17 Oct 2013 15:32:10 -0400
Message-ID: <F41DF3A6EE7144CF9A90BB43D9FD5E84@Gantry> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
We are assisting in the system administration of a partner that uses PostGres in a mission critical position in their system. They have mail servers and other things that rely on 24/7 availability for the postgres server. They are running postgres 9.04 on redhat linux (2.6.32-131.0.15.el6.x86_64). This is running on one old machine, and thus does not really provide the liability they looking for.
I had the thought that I could set up another server as a slave, then promote the slave in the event it’s necessary. I was trying I made a system that watches for a change in the IP number number of the server in dns, then downs the primary, swaps primary-secondary configs in the primary, restarts the primary, then does the same in the secondary. This actually worked on the first test from failing the primary to the secondary. The problem came when I stried to switch it back. When I tried to restart the original primary as secondary, it failed saying the database was corrupted.
There are a couple of possible solutions to this, but I’m starting to think that what they probably really want anyway is a Postgres server cluster of two servers that stay in synch with each other, and can simultaneously accept read and write requests. Are there any opinions here about the best way to set this up?
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: PG server clustering
In-Reply-To: <F41DF3A6EE7144CF9A90BB43D9FD5E84@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