| 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 11:03:21 |
| Message-ID: | CA+U5nMK7jWSp3tx5Ab_UMHyQ2-MxyY3Jr7PNWMAVxaQ20=AHqQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-cluster-hackers |
On 13 March 2015 at 10:28, Deole, Pushkar (Pushkar) <pdeole(at)avaya(dot)com> wrote:
> Can you elaborate on " Bad idea to do that automatically."
>
> In production, that has to happen automatically, isn't it? There won't be an administrator available all the time to do a failover in case primary goes down..
Automatic failover is OK. Automatic failback is not OK.
>> 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 | Radovan Jablonovsky | 2015-03-16 17:35:32 | postgresq foreign data wrapper with foreign constrain checking, distributed (multi nodes) query execution. |
| Previous Message | Deole, Pushkar (Pushkar) | 2015-03-13 10:28:25 | Re: Asynchronous streaming replication in postgresql |