[Pgpool-general] pgpool setup scenarios
Johnny Tan
johnny at paperlesspost.com
Wed Jul 27 19:23:47 UTC 2011
On Fri, Jul 22, 2011 at 4:17 PM, Josh Berkus <josh at agliodbs.com> wrote:
>
>> * install on its own server or, ideally, set of servers (with heartbeat, etc.)
>
> This is preferred. Installing pgpool on the database servers is pretty
> pointless.
Thanks Josh. How do you make pgpool highly available?
At first, I thought pgpool-ha existed for that reason, but it appears
to be more for failover from a primary backend Postgres node to a
standby one (a feature which pgpool-II now incorporates, right?).
But pgpool itself remains a single point of failure. I'm trying to
figure out the best way to make pgpool itself HA. The simplest seems
to be to setup heartbeat between two pgpool servers with a virtual IP
and point clients to the virtual IP.
Since it's stateless, it seems like sticking a loadbalancer in front
of two (or more) pgpool servers could also work. (Although your
loadbalancer now becomes the new SPOF :-), unless you have two.)
Thoughts?
johnny
More information about the Pgpool-general
mailing list