Re: [PG19] Sequence sync stops when the subscription owner can't SET ROLE to a sequence owner

On Sat, Oct 17, 2026 at 4:19 AM Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> wrote:
>
> Hello
>
> The patch also extends 036_sequences.pl, the new check fails without the fix.
Hi Zsolt,

The fix looks right to me, but the new test in 036_sequences.pl fails
intermittently (about once in 15 runs here). When it fails, it times
out waiting for the "insufficient privileges on subscriber sequence"
WARNING, because the sequencesync worker ends up syncing regress_s4
without any error.

The CONNECTION and password_required changes in the test setup cause
the apply worker to restart, and it can come back up before the OWNER
TO change commits. In that case it still has the old superuser owner,
so the sequencesync worker runs as superuser, member_can_set_role()
succeeds, and no WARNING is emitted.

The test needs to make sure the workers have restarted with the new
owner before running REFRESH SEQUENCES.

Regards,
Ajin Cherian
Fujitsu Australia