My idea was, and I didn't test it, it's: Server 1 Server 2 postgres 9 A postgres9 B pgpool A pgpool B application A application B
The idea was : - pgpool A is active, it's doing a streaming replication with postgres A and B. -application A is communicating with pgpool A. - application B is communicating with pgpool A. if the server 1 goes down, pgpool is starting, doing the failover command. The application B detect that pgpoolA is not working anymore, and try to communicate with pgpoolB. On Thu, Mar 31, 2011 at 9:33 AM, Erwan <[email protected]> wrote: > Hi Sean > > On 03/31/2011 02:03 AM, Sean Tegtmeyer wrote: > > > Therefore pgpool-II does not provide a fail-over solution in the case that > the box running pgpool-II goes down, and it would be up to the user of > pgpool-II to implement a fail-over solution that would start pgpool-II on > another box, correct? Thanks for the help. > > > > But you can easily use system like ucarp ( > http://www.ucarp.org/project/ucarp) to share common virtual IP addresses > and to provide automatic failover. > It works nice! > > /Erwan > > _______________________________________________ > 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
