| From: | Thomas Poty <thomas(dot)poty(at)gmail(dot)com> |
|---|---|
| To: | soumitra bhandary <soumitra(dot)bhandary(at)hotmail(dot)com> |
| Cc: | "shreeyansh2014(at)gmail(dot)com" <shreeyansh2014(at)gmail(dot)com>, "pgsql-admin(at)lists(dot)postgresql(dot)org" <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Configuration of django with master slave replication Postgres |
| Date: | 2019-04-02 12:22:00 |
| Message-ID: | CAN_ctnivSuXmBjKHaJyn_iOrTioDcFZnRnYLMU1zg1rEm3CAPw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
As you are using pg 9.5, these links may help :
https://severalnines.com/blog/postgresql-load-balancing-using-haproxy-keepalived
https://clusterlabs.github.io/PAF/
Le mar. 2 avr. 2019 à 13:50, soumitra bhandary <
soumitra(dot)bhandary(at)hotmail(dot)com> a écrit :
>
> Hi
> Does anyone have any idea with django how to configure multiple dsn that
> will automatically switch to new Postgres master host in case of failover
> happens to previous master and auto promotion of new master is done with
> repmgr.
>
>
> My configuration is as below
>
> Master and asynchronous slave node . Repmgrd is configured to take care of
> autofailover and promotion of new master node.
>
> But from application side with django how to make datasource so that it
> automatically switches to new master node in case of failover.
> Please share the steps.
>
>
> Sent from my iPhone
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Prince Pathria | 2019-04-02 20:39:35 | Re: Configuration of django with master slave replication Postgres |
| Previous Message | Shreeyansh Dba | 2019-04-02 12:21:38 | Re: trying to analyze deadlock |