Message-ID: <a50f44d5dbb3bef00594c7539479b29ca464a0dc.camel@cybertec.at>
Subject: Re: recovery.conf and archive_cleanup_command
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Rita <rmorgan466@gmail.com>, pgsql-novice@postgresql.org
Date: Sun, 09 Oct 2022 19:32:51 +0200
In-Reply-To: 
 <CAOF-KfhGM28vyE+HShrfnTNx8PYBeyTkiNGDA_xPF1DDS_PEHg@mail.gmail.com>
References: 
	<CAOF-KfhGM28vyE+HShrfnTNx8PYBeyTkiNGDA_xPF1DDS_PEHg@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.42.4 (3.42.4-2.fc35) 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/a50f44d5dbb3bef00594c7539479b29ca464a0dc.camel%40cybertec.at>
Precedence: bulk

On Sat, 2022-10-08 at 08:51 -0400, Rita wrote:
> I have primary and standby replication setup.
> 
> On my primary the archive directory is rather large (30GB) and growing. On my standby I have recovery.conf which has 
> archive_cleanup_command = 'pg_archivecleanup -d /var/lib/pgsql/11/data/archive %r'
> 
> I was under the impression this line would remove data from my primary AND standby. Is that not the case?

That depends on your PostgreSQL version, for instance.

Also, it depends on whether the standby server is running and actually recovering.
Finally, it depends on whether the standby can execute the command successfully or not.

Did you look at the standby's logs?

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com