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
References: 
 <CALhHtcBtq3NiORvFMPdq_TY508Lmif99r_fcskyfN7Mu7N7Fsw@mail.gmail.com>
Date: Thu, 14 Jan 2021 09:51:24 -0600
In-Reply-To: 
 <CALhHtcBtq3NiORvFMPdq_TY508Lmif99r_fcskyfN7Mu7N7Fsw@mail.gmail.com>
	(Yambu's message of "Thu, 14 Jan 2021 14:18:50 +0200")
Message-ID: <87r1mno6tf.fsf@jsievers.enova.com>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

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=C2=A0below 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=C2=A0
>
> trigger_file =3D '/tmp/postgresql.trigger.5432'=C2=A0 =C2=A0
>
> 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
>
>
> =C2=A0
>
>

--=20
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net