| From: | "Kevin Grittner" <kgrittn(at)mail(dot)com> |
|---|---|
| To: | "Keith Ouellette" <Keith(dot)Ouellette(at)Airgas(dot)com>, pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: WAL replication question |
| Date: | 2013-01-21 21:07:54 |
| Message-ID: | 20130121210754.120610@gmx.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
Keith Ouellette wrote:
> I am using the trigger file capability to "promote" the Slave in
> the event that the Master fails.
> when the former Master comes back on line, is there a way to make
> it a slave (adding the recovery.conf file) without restarting the
> PostgreSQL process? I currently do this with a restart, which
> works well, but we are using Pacemaker and the PostgreSQL
> resource goes away and takes the node down until it comes up. We
> would rather the node not go down if possible.
That's confusing -- if the master node fails, how can it still be
up?
Once you fail over, you should take care that the old master node
is good and truly down until it can be started as a slave. You
will need to copy from the new master to the node which is to be
the new slave before you do that. And yes, add the recovery.conf.
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Keith Ouellette | 2013-01-22 13:22:39 | Re: WAL replication question |
| Previous Message | Jack Kaufman | 2013-01-21 19:43:04 | Re: Determine the name of the calling function |