From: | Payal Singh <payal(at)omniti(dot)com> |
---|---|
To: | metsarin <metsarin(at)yahoo(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: failover and switchover in postgresql |
Date: | 2013-10-25 17:02:13 |
Message-ID: | CANUg7LBkdjDX+3FSRyiX+5tB0S343ObtRTtrb2HahogcgtrVMQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
After performing a failover, the old slave becomes the new master, but the
opposite is not true, that is, the old master does not automatically become
the slave. You will need to set up replication from the new master to the
to-be slave to be able to switch back.
Payal Singh,
OmniTi Computer Consulting Inc.
Junior Database Architect,
Phone: 240.646.0770 x 253
On Fri, Oct 25, 2013 at 4:48 AM, metsarin <metsarin(at)yahoo(dot)com> wrote:
> Dear Community!
>
> For example, I have two servers. First is the primary server and second is
> the slave server. I need slave server to become primary (temp) during
> primary server is down. Then old primary was fixed. I need old primary
> server is the primary server and then old slave server (new primary (temp))
> to become slave server. Pls help me to explain how solve this problem.
> Thanks!
>
>
>
> --
> View this message in context:
> http://postgresql.1045698.n5.nabble.com/failover-and-switchover-in-postgresql-tp5775885.html
> Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
>
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin
>
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Ribe | 2013-10-25 17:07:06 | Re: failover and switchover in postgresql |
Previous Message | Steven Hartland | 2013-10-25 16:19:54 | Re: ZFS-FreeBSD + postgresql performance |