From: | "Deole, Pushkar (Pushkar)" <pdeole(at)avaya(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Asynchronous replication in postgresql |
Date: | 2015-03-11 10:27:51 |
Message-ID: | 78A4D6BFBAA5BA49A5E94DA00A6A76E3535354@AZ-FFEXMB04.global.avaya.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I am new to postgresql and evaluating the streaming replication for my use case. My use case is:
1. Need to replicate data from primary database (master) to secondary database (slave) asynchronously.
2. If master goes down, the slave should automatically be promoted to master.
3. Later, when the original primary server (original master) is brought up again, it should obtain back its master role and the new master should assume the slave again as it was with original setup.
For #1, the streaming replication of postgresql is good enough.
For #2, we need to create the trigger file. How can we do this automatically?
For #3, this seems to be quite complicated. Is this even possible using streaming replication? If yes, how can this be achieved?
Your help is greatly appreciated in this regard.
Thank you very much..
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Inder | 2015-03-11 10:54:56 | Basic Question on Point In Time Recovery |
Previous Message | Tom Lane | 2015-03-11 02:09:10 | Re: pg_dump search path issue |