Re: Synchronizing slots from primary to standby - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Synchronizing slots from primary to standby
Date
Msg-id 7a005e90-debb-c485-62b4-dbb49d63e5a7@enterprisedb.com
Whole thread Raw
In response to Re: Synchronizing slots from primary to standby  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On 24.11.21 07:11, Masahiko Sawada wrote:
> I haven’t looked at the patch deeply but regarding 007_sync_rep.pl,
> the tests seem to fail since the tests rely on the order of the wal
> sender array on the shared memory. Since a background worker for
> synchronizing replication slots periodically connects to the walsender
> on the primary and disconnects, it breaks the assumption of the order.
> Regarding 010_logical_decoding_timelines.pl, I guess that the patch
> breaks the test because the background worker for synchronizing slots
> on the replica periodically advances the replica's slot. I think we
> need to have a way to disable the slot synchronization or to specify
> the slot name to sync with the primary. I'm not sure we already
> discussed this topic but I think we need it at least for testing
> purposes.

This has been addressed by patch v2 that adds such a setting.




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Synchronizing slots from primary to standby
Next
From: Tom Lane
Date:
Subject: Re: pg_dump versus ancient server versions