Re: Remove Standby (SLAVE) from Primary (MASTER) - Postgres9.1 - Mailing list pgsql-general
| From | Joanna Xu |
|---|---|
| Subject | Re: Remove Standby (SLAVE) from Primary (MASTER) - Postgres9.1 |
| Date | |
| Msg-id | 9CAA34031E7FE348AE75D1F0C34F85D0B0DE7446@USSTLDAGBE2.corp.amdocs.com Whole thread Raw |
| In response to | Re: Remove Standby (SLAVE) from Primary (MASTER) - Postgres9.1 (melvin6925 <melvin6925@gmail.com>) |
| List | pgsql-general |
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
+1 613 595 5234
AMDOCS | EMBRACE CHALLENGE EXPERIENCE SUCCESS
POLICY CONTROL IN THE FAST LANE
What’s making policy control strategic in 2015 and beyond? Check out the top ten factors driving change…
From: melvin6925 [mailto:melvin6925@gmail.com]
Sent: Wednesday, October 26, 2016 8:16 PM
To: Adrian Klaver <adrian.klaver@aklaver.com>; Michael Paquier <michael.paquier@gmail.com>; Joanna Xu <Joanna.Xu@amdocs.com>
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Remove Standby (SLAVE) from Primary (MASTER) - Postgres9.1
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@aklaver.com>
Date: 10/26/16 19:50 (GMT-05:00)
To: Michael Paquier <michael.paquier@gmail.com>, Joanna Xu <Joanna.Xu@amdocs.com>
Subject: Re: [GENERAL] Remove Standby (SLAVE) from Primary (MASTER) - Postgres9.1
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
pgsql-general by date: