If you dig deeper into pgpool-II you will find that it does not have failover logic. Its intention is to pool connections and distribute query load among replicas, but it cannot differentiate node failure from network partition and cannot promote a standby to master in the case of failure.
*Will J. Dunn* *willjdunn.com <http://willjdunn.com>* On Tue, Jul 21, 2015 at 1:55 PM, Aviel Buskila <avie...@gmail.com> wrote: > Can you link me up to a good tutorial using pgpool-II? > > 2015-07-21 20:02 GMT+03:00 Joshua D. Drake <j...@commandprompt.com>: > >> >> On 07/21/2015 08:34 AM, William Dunn wrote: >> >>> Hello Aviel, >>> >>> On Tue, Jul 21, 2015 at 3:56 AM, Aviel Buskila <avie...@gmail.com >>> <mailto:avie...@gmail.com>> wrote: >>> >>> How can I set a highly available postgresql in a share-nothing >>> architecture? >>> >>> I suggest you review the official documentation on high-availability >>> configurations linked below: >>> http://www.postgresql.org/docs/current/static/high-availability.html >>> >>> The most common configuration is to use PostgreSQL's built in >>> master/standby streaming replication. However you will need to develop >>> any fail-over logic you need yourself or use a third party tool such as >>> EnterpriseDB's Failover Manager. >>> >> >> Or use already available open source tools such as Pgpool-II or Linux-HA. >> >> Sincerely, >> JD >> >> -- >> Command Prompt, Inc. - http://www.commandprompt.com/ 503-667-4564 >> PostgreSQL Centered full stack support, consulting and development. >> Announcing "I'm offended" is basically telling the world you can't >> control your own emotions, so everyone else should do it for you. >> > >
