On Tuesday, August 27, 2024 10:59 AM Peter Smith <smithpb2...@gmail.com> wrote:
>
> ~~~
>
> 3.
> +# Enable track_commit_timestamp to detect origin-differ conflicts in
> +logical # replication. Reduce wal_retrieve_retry_interval to 1ms to
> +accelerate the # restart of the logical replication worker after
> encountering a
> conflict.
> +$node_subscriber->append_conf(
> + 'postgresql.conf', q{
> +track_commit_timestamp = on
> +wal_retrieve_retry_interval = 1ms
> +});
>
> Later, after CDR resolvers are implemented, it might be good to revisit these
> conflict test cases and re-write them to use some conflict resolvers like
> 'skip'.
> Then the subscriber won't give ERRORs and restart apply workers all the time
> behind the scenes, so you won't need the above configuration for accelerating
> the worker restarts. In other words, running these tests might be more
> efficient
> if you can avoid restarting workers all the time.
>
> I suggest putting an XXX comment here as a reminder that these tests should
> be revisited to make use of conflict resolvers in the future.I think it would be too early to mention the resolution implementation detail in the comments considering that the resolution is still not RFC. Also, I think reducing wal_retrieve_retry_interval is a reasonable way to speed up the test in this case because the test is not letting the worker to restart all the time, the error causes the restart will be resolved immediately after the stats check. So, I think adding XXX is not very appropriate. Other comments look good to me. I slightly adjusted few words and merged the changes. Thanks ! Here is V3 patch. Best Regards, Hou zj
v3-0001-Collect-statistics-about-conflicts-in-logical-rep.patch
Description: v3-0001-Collect-statistics-about-conflicts-in-logical-rep.patch
