From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | "Deole, Pushkar (Pushkar)" <pdeole(at)avaya(dot)com> |
Cc: | pgsql-cluster-hackers(at)postgresql(dot)org |
Subject: | Re: Asynchronous streaming replication in postgresql |
Date: | 2015-03-12 06:15:14 |
Message-ID: | CAECtzeXj-WqZqah6kvvFm4_6i6X5Mg-VY+DNydGQbK7WNhxFJw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-cluster-hackers |
Le 12 mars 2015 06:57, "Deole, Pushkar (Pushkar)" <pdeole(at)avaya(dot)com> a
écrit :
>
> 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 in slave. This can be done
manually. How can we do this automatically?
>
> For #3, this seems to be quite complicated. Is this possible using
streaming replication and if yes then how can this be achieved?
>
This is doable with pacemaker or something alike. Wether this is a smart
move or not is definitely arguable :-) I know for sure that I don't want
that kind of automatic actions on my servers.
BTW, this isn't the list you should use for that kind of questions. Pgsql -
general would be better.
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2015-03-13 09:52:56 | Re: Asynchronous streaming replication in postgresql |
Previous Message | Deole, Pushkar (Pushkar) | 2015-03-12 05:56:49 | Asynchronous streaming replication in postgresql |