is the archive command even needed? I can see my standby fully synced.
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
The archive command stores the WAL in a local directory. That's what I said earlier.
Hi,
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.
--
--
--- Get your facts first, then you can distort them as you please.--
--
--
--- Get your facts first, then you can distort them as you please.--