Re: Turn off streaming replication - leaving Master running

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Andy Erskine <andy(dot)erskine(at)jds(dot)net(dot)au>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: Turn off streaming replication - leaving Master running
Date: 2015-06-30 05:47:29
Message-ID: CAB7nPqRwpWYX56HqDHR6OLCQBagDRCkfmRqv-XV6HG0wb56tbA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Jun 30, 2015 at 2:29 PM, Andy Erskine <andy(dot)erskine(at)jds(dot)net(dot)au>
wrote:

> Ok so a question i should have asked at the very beginning ..
>
> If i touch my trigger file - promoting the secondary to a master - will
> that in anyway effect the master thats already running ?
> IE no files on the master will change ?
>

Streaming replication is designed to let the master run properly when a
standby disconnects.

> Then all i'll have to do is shutdown the secondary when i've finished and
> run the basebackup process again to restore replication (and change
> recovery.done - conf again.
>

Yes.

Now something that has been mentioned by the others: isn't your standby
here for a reason? Like in case of failure don't you have a process to
failover automatically? Perhaps you are shooting yourself in the foot by
unplugging this standby, hence you should, and other recommend the same,
simply let the existing standby alone and create a new instance by taking a
new base backup from either the master or the standby and use it for your
tests. Then eliminate the node you created. In short: avoid doing stupid
things...
--
Michael

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Andy Erskine 2015-06-30 05:55:01 Re: Turn off streaming replication - leaving Master running
Previous Message Andy Erskine 2015-06-30 05:29:38 Re: Turn off streaming replication - leaving Master running