Re: sequencesync worker race with REFRESH SEQUENCES

On Thu, 30 Jul 2026 at 04:07, Peter Smith <smithpb2250(at)gmail(dot)com> wrote:
>
> FYI, somehow the "rather than" wording of the above comment became a
> "rathen then" typo in the master code [1].

Thanks for reporting this. The attached patch addresses the issue.

In addition, it also addresses the last remaining finding (Finding 13:
"REFRESH SEQUENCES warning misattributes a `copy_data` request the
command cannot express"). The warning emitted by
check_publications_origin_sequences() is triggered when a subscription
with origin = NONE synchronizes sequence values that may have
originated from another subscription. However, the existing warning is
phrased in terms of copy_data and copying data, which is appropriate
for table synchronization but misleading for sequence synchronization.
The patch rewords the warning, detail, and hint to describe sequence
synchronization and the associated origin = NONE semantics more
accurately.

Regards,
Vignesh