is the archive command even needed? I can see my standby fully synced.
On Fri, Oct 14, 2022 at 5:27 AM Guillaume Lelarge
wrote:
> Le jeu. 13 oct. 2022 à 12:42, Rita a écrit :
>
>> The primary's recovery.conf looks like this
>>
>> listen_address='*'
>> wal_level=replica
>> synchronous_commit=loc
Le jeu. 13 oct. 2022 à 12:42, Rita a écrit :
> 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
> synchr
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, 2
Hi,
Le dim. 9 oct. 2022 à 13:54, Rita 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/ar
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 d
