From: Jerry Sievers <gsievers19@comcast.net>
To: Yambu <hyambu@gmail.com>
Cc: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: Re: Removing second slave server
Date: Thu, 14 Jan 2021 09:51:24 -0600
Message-ID: <87r1mno6tf.fsf@jsievers.enova.com> (raw)
In-Reply-To: <CALhHtcBtq3NiORvFMPdq_TY508Lmif99r_fcskyfN7Mu7N7Fsw@mail.gmail.com>
References: <CALhHtcBtq3NiORvFMPdq_TY508Lmif99r_fcskyfN7Mu7N7Fsw@mail.gmail.com>
Yambu <hyambu@gmail.com> writes:
> Hello
>
> I want to reinstall my second slave server and I have to stop
> replication.
>
> May i know if it's enough to just run the command below on the second
> slave
>
> touch /tmp/postgresql.trigger.5432
You don't even have to do that if you're going to decom and put the
server up again.
>
> Trigger file in recovery.conf is
>
> trigger_file = '/tmp/postgresql.trigger.5432'
>
> Do i need to do anything on the master server so that wal files do
> not build up since the second slave is no longer active?
Perhaps, if you are using a replication slot which is typical on $recent
releases such as Pg10.
After the standby is down, drop the related replication slot on your
primary else you'll retain WAL files unnecessarily and could fill the
disk.
HTH
>
> Im using PG v10,streaming replication
>
> regards
>
>
>
>
>
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: gsievers19@comcast.net, hyambu@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Removing second slave server
In-Reply-To: <87r1mno6tf.fsf@jsievers.enova.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox