Re: Removing second slave server

From: Jerry Sievers <gsievers19(at)comcast(dot)net>
To: Yambu <hyambu(at)gmail(dot)com>
Cc: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: Removing second slave server
Date: 2021-01-14 15:51:24
Message-ID: 87r1mno6tf.fsf@jsievers.enova.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Yambu <hyambu(at)gmail(dot)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(dot)consulting(at)comcast(dot)net

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message franklin ferreira de lima 2021-01-14 16:02:45 Re: Removing second slave server
Previous Message franklin ferreira de lima 2021-01-14 15:16:23 Re: PostgreSQL replication failover