Re: recovery.conf and archive files

Поиск
Список
Период
Сортировка
От Rita
Тема Re: recovery.conf and archive files
Дата
Msg-id CAOF-KfhHsKwP8M7CQb47i4Ek=JeLDpCVrsk1Xe6O0PZ2SC6LZg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: recovery.conf and archive files  (Guillaume Lelarge <guillaume@lelarge.info>)
Ответы Re: recovery.conf and archive files  (Guillaume Lelarge <guillaume@lelarge.info>)
Список 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@lelarge.info> wrote:
Hi,

Le dim. 9 oct. 2022 à 13:54, Rita <rmorgan466@gmail.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.--

В списке pgsql-general по дате отправления:

Предыдущее
От: Julien Rouhaud
Дата:
Сообщение: Re: Problem with LATERAL
Следующее
От: Adrian Klaver
Дата:
Сообщение: Exponentiation confusion