Re: sequencesync worker race with REFRESH SEQUENCES

On Wed, Jul 22, 2026 at 9:09 AM shveta malik <shveta(dot)malik(at)gmail(dot)com> wrote:
>
> On Wed, Jul 22, 2026 at 8:58 AM shveta malik <shveta(dot)malik(at)gmail(dot)com> wrote:
> >
> > When this idea was discussed earlier, I had asked whether we could
> > move the version check from copy_sequences() to the apply worker
> > (ProcessSequencesForSync) before it starts sequnece sync worker. The
> > intention was to avoid repeatedly starting the sequence-sync worker
> > only for it to exit in copy_sequences(). The apply worker itself could
> > report an error similar to how the backend reports it during REFRESH.
> > Thoughts?
>
> Apply-worker can report a WARNING instead of ERROR. It's no use if the
> apply worker keeps exiting and restarting instead of the seqsync
> worker.
>

I feel the WARNINGs can go unnoticed. Anyway, we do restart sync/apply
workers on ERROR or parameter change, so it seems okay to give ERROR
from sequence syncworker itself.

--
With Regards,
Amit Kapila.