From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | "Deole, Pushkar (Pushkar)" <pdeole(at)avaya(dot)com> |
Cc: | "pgsql-cluster-hackers(at)postgresql(dot)org" <pgsql-cluster-hackers(at)postgresql(dot)org> |
Subject: | Re: Asynchronous streaming replication in postgresql |
Date: | 2015-03-13 09:52:56 |
Message-ID: | CA+U5nMJ0emE2E2uBGZ5k5KyJ1chy8T2d=-uRFmQ2BqSkpiq0xw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cluster-hackers |
On 12 March 2015 at 05:56, Deole, Pushkar (Pushkar) <pdeole(at)avaya(dot)com> wrote:
> 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 in slave. This can be done
> manually. How can we do this automatically?
Look at repmgr, it does what you need.
> For #3, this seems to be quite complicated. Is this possible using streaming
> replication and if yes then how can this be achieved?
Bad idea to do that automatically.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, RemoteDBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Deole, Pushkar (Pushkar) | 2015-03-13 10:28:25 | Re: Asynchronous streaming replication in postgresql |
Previous Message | Guillaume Lelarge | 2015-03-12 06:15:14 | Re: Asynchronous streaming replication in postgresql |