From: Scott Marlowe <scott.marlowe@gmail.com>
To: Jamie Tufnell <diesql@googlemail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Best option for expanding beyond 1 pg server in this situation
Date: Tue, 25 Nov 2008 22:12:44 -0700
Message-ID: <dcc563d10811252112w3e5145a4sb58d062a724d1a5e@mail.gmail.com> (raw)
In-Reply-To: <b0a4f3350811251948u21b90730p604d93a4b97c71c2@mail.gmail.com>
References: <b0a4f3350811251948u21b90730p604d93a4b97c71c2@mail.gmail.com>
On Tue, Nov 25, 2008 at 8:48 PM, Jamie Tufnell <diesql@googlemail.com> wrote:
> Hi,
>
> We have been wanting to HA our pgsql server for some time now. We're
> actually reaching the limits of our current server now, so there is a
> pressing need to do something to ease the load too.
>
> There are several individual solutions to both of these problems. I
> was hoping I could get some advice from someone more experienced
> though, about what the simplest most effective way of moving forward
> would be? Hopefully I can squash both HA and LB with the same
> solution.
>
> So far I've narrowed it down to
>
> Slony-I master/slave replication with failover
We use this where I work and it works quite well. We have some custom
scripts that detect failure of the master db and initiates failover to
the slave if necessary. We do this from the applicaiton level.
> pgpool-II with heartbeat for failover. The pgpool-II configuration
> matrix (http://pgpool.projects.postgresql.org/) isn't terribly clear
> (there's no legend) but it leads me to believe failover and load
> balancing are mutually exclusive options. Is that so?
Seems to be. I haven't played with pgpool in a long time so don't
take my word as authoritative.
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: scott.marlowe@gmail.com, diesql@googlemail.com
Subject: Re: Best option for expanding beyond 1 pg server in this situation
In-Reply-To: <dcc563d10811252112w3e5145a4sb58d062a724d1a5e@mail.gmail.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