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, Joanna Xu Senior Oracle DBA Data Experience Solution BU
AMDOCS |
EMBRACE CHALLENGE
EXPERIENCE SUCCESS POLICY CONTROL IN THE FAST LANE
From: melvin6925 [mailto:melvin6925@xxxxxxxxx]
It's simple just look in recovery. conf on slave and put stated trigger. then slave becomes stand alone. Sent via the Samsung Galaxy S® 6, an AT&T 4G LTE smartphone -------- Original message -------- From: Adrian Klaver <adrian.klaver@xxxxxxxxxxx>
Date: 10/26/16 19:50 (GMT-05:00) To: Michael Paquier <michael.paquier@xxxxxxxxx>, Joanna Xu <Joanna.Xu@xxxxxxxxxx>
Subject: Re: [GENERAL] Remove Standby (SLAVE) from Primary (MASTER) - Postgres9.1
On 10/26/2016 04:43 PM, Michael Paquier wrote: |