Message-ID: <F41DF3A6EE7144CF9A90BB43D9FD5E84@Gantry>
From: "Joseph Mays" <mays@win.net>
To: <pgsql-admin@postgresql.org>
Subject: PG server clustering
Date: Thu, 17 Oct 2013 15:32:10 -0400
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="----=_NextPart_000_0046_01CECB4E.0BFC1300"
Importance: Normal
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

This is a multi-part message in MIME format.

------=_NextPart_000_0046_01CECB4E.0BFC1300
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=99s 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=E2=80=99m =
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?

------=_NextPart_000_0046_01CECB4E.0BFC1300
Content-Type: text/html;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable

<HTML><HEAD></HEAD>
<BODY dir=3Dltr>
<DIV dir=3Dltr>
<DIV style=3D"FONT-SIZE: 12pt; FONT-FAMILY: 'Calibri'; COLOR: #000000">
<DIV>We are assisting in the system administration of a partner that =
uses=20
PostGres in a mission critical position in their system. They have mail =
servers=20
and other things that rely on 24/7 availability for the postgres server. =
They=20
are running postgres 9.04 on redhat linux (2.6.32-131.0.15.el6.x86_64). =
This is=20
running on one old machine, and thus does not really provide the =
liability they=20
looking for.</DIV>
<DIV>&nbsp;</DIV>
<DIV>I had the thought that I could set up another server as a slave, =
then=20
promote the slave in the event it=E2=80=99s necessary. I was trying I =
made a system that=20
watches for a change in the IP number number of the server in dns, then =
downs=20
the primary, swaps primary-secondary configs in the primary, restarts =
the=20
primary, then does the same in the secondary. This actually worked on =
the first=20
test from failing the primary to the secondary. The problem came when I =
stried=20
to switch it back. When I tried to restart the original primary as =
secondary, it=20
failed saying the database was corrupted.</DIV>
<DIV>&nbsp;</DIV>
<DIV>There are a couple of possible solutions to this, but I=E2=80=99m =
starting to think=20
that what they probably really want anyway is a Postgres server cluster =
of two=20
servers that stay in synch with each other, and can simultaneously =
accept read=20
and write requests. Are there any opinions here about the best way to =
set this=20
up?</DIV>
<DIV>&nbsp;</DIV></DIV></DIV></BODY></HTML>

------=_NextPart_000_0046_01CECB4E.0BFC1300--