Re: recovery.conf and archive files

From: Rita <rmorgan466(at)gmail(dot)com>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org>
Subject: Re: recovery.conf and archive files
Date: 2022-10-13 10:41:51
Message-ID: CAOF-KfhHsKwP8M7CQb47i4Ek=JeLDpCVrsk1Xe6O0PZ2SC6LZg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

The primary's recovery.conf looks like this

listen_address='*'
wal_level=replica
synchronous_commit=local
archive_move = on
archive_command = 'cp %p /var/lib/pgsql/11/data/archive/%f'
max_wal_senders = 10
wal_keep_segments=10
synchronous_standby_names='standby0'
wal_log_hints=on

On Sun, Oct 9, 2022 at 8:45 AM Guillaume Lelarge <guillaume(at)lelarge(dot)info>
wrote:

> Hi,
>
> Le dim. 9 oct. 2022 à 13:54, Rita <rmorgan466(at)gmail(dot)com> a écrit :
>
>> 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?
>>
>>
> pg_archivecleanup will clean up the *local* directory. It won't clean up
> the archive directory if it's stored on the primary.
>
> If I misunderstood your issue, it would be great to send us the
> postgresql.conf file from your primary.
>
>
> --
> Guillaume.
>

--
--- Get your facts first, then you can distort them as you please.--

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ajin Cherian 2022-10-13 12:46:39 Re: Support logical replication of DDLs
Previous Message Julien Rouhaud 2022-10-13 08:34:13 Re: Problem with LATERAL