Thanks for your suggestions. We are not using Heartbeat, plus we need AP0 and AP1 connected to their own pgpool-II instance (refer to the original message). However, only one of those APx is going to be active at a certain time, so there should be only one source of data incoming to the database at any time. Since pgpool-II is a new implementation, we are trying to accommodate it to our framework, and Heartbeat is not an option for us right now.
In regard of the sequence of the installation, jumping back and forth for configuring the servers is definitely not what we need. I have an schema of what can be done. As soon as I have it planned, I'll post it for anyone who is interested on it. Thanks Jaume. Daniel -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jaume Sabater Sent: Monday, December 22, 2008 3:25 AM To: [email protected] Subject: Re: [Pgpool-general] Detecting type of failure On Fri, Dec 19, 2008 at 9:32 PM, <[email protected]> wrote: > Some suggestions? Install PostgreSQL on the first node. Install pgpool-II on first node and configure only one backend server. Install PostgreSQL on the second node. Configure the second backend on the first pgpool-II. Configure the second pgpool-II, configure both backends. Do not start it. Configure Heartbeat. Start heartbeat. If you don't have Heartbeat in mind, then you don't want two pgpool-II simultaneously active against two backends. -- Jaume Sabater http://linuxsilo.net/ "Ubi sapientas ibi libertas" _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general _______________________________________________ Pgpool-general mailing list [email protected] http://pgfoundry.org/mailman/listinfo/pgpool-general
