Re: Remove Standby (SLAVE) from Primary (MASTER) - Postgres9.1

Here is the current recovery.conf on slave. Does the trigger_file need to be changed? If it does, can you give me an example?

# Note that recovery.conf must be in $PGDATA directory.

# Specifies whether to start the server as a standby. In streaming replication,

# this parameter must to be set to on.

standby_mode          = 'on'

#recovery_target_timeline = 'latest'

# Specifies a connection string which is used for the standby server to connect

# with the primary.

primary_conninfo = 'host=10.53.199.61 port=5432 user=postgres'

# Specifies a command to load archive segments from the WAL archive. If

# wal_keep_segments is a high enough number to retain the WAL segments

# required for the standby server, this may not be necessary. But

# a large workload can cause segments to be recycled before the standby

# is fully synchronized, requiring you to start again from a new base backup.

restore_command = 'cp /opt/postgres/9.1/archive/%f %p'

trigger_file='/opt/postgres/9.1/data/trigger'

Thanks,

On 10/26/2016 04:43 PM, Michael Paquier wrote:
> On Wed, Oct 26, 2016 at 11:18 PM, Joanna Xu <Joanna.Xu@amdocs.com> wrote:
>> I’ve been looking for a procedure (step by step) on how to remove Standby
>> (SLAVE) from Primary (MASTER) for Postgres9.1 in google and the archived
>> postings, but no luck.
>
> Standby and master servers are two separate Postgres instances. So if
> you would like to remove a standby from a cluster. You just need to
> basically stop it, then remove its data folder. And you are done.
> There is no complicated science here.

Not sure that is what OP wants. From the original post:

" ...
2.       After the standby is removed from the primary, both of nodes
are in standalone configuration. "



--
Adrian Klaver
adrian.klaver@aklaver.com


--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general