From: | Subhankar Chattopadhyay <subho(dot)atg(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Lag in asynchronous replication |
Date: | 2017-03-24 06:11:51 |
Message-ID: | CAPg1NnEMKLOT4iJ2D51ekKr9ngggOTjxdO-JFMgJw0CrZyS47w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi Michael,
Are you asking to have slave with synchronous replication?
Regards,
SUBHANKAR CHATTOPADHYAY
On 24 Mar 2017 09:33, "Michael Paquier" <michael(dot)paquier(at)gmail(dot)com> wrote:
> On Thu, Mar 23, 2017 at 11:37 PM, Subhankar Chattopadhyay
> <subho(dot)atg(at)gmail(dot)com> wrote:
> > in case of automated failover i want to check if slave is lagging from
> > master and only if it is in sync, i want to do failover. But I am
> working in
> > a virtual cloud environment so by that time the master VM may not be
> > available to me. How can i check the lag in that case ?
>
> Is your environment switching dynamically to async if the lag is too
> important? If not, once you have reached a sync state, the master
> would wait for all transactions commits to complete on the slave, so
> once the client has received a commit confirmation you have the
> guarantee that the data is already flushed on the slave. In this case
> you don't need to know what happens on the master.
> --
> Michael
>
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2017-03-24 06:46:52 | Re: Lag in asynchronous replication |
Previous Message | Michael Paquier | 2017-03-24 04:03:53 | Re: Lag in asynchronous replication |