On Wed, Feb 18, 2026 at 12:36 PM shveta malik <[email protected]> wrote: > > I tested a few scenarios on the latest patch. Sequence sync worker did > not stop in below scenarios: > > 1) When the subscription was disabled. > 2) When the only publication for sequences was dropped from > subscription ( ALTER SUBSCRIPTION sub1 DROP PUBLICATION pub_seq;) > 3) When all sequences were dropped on sub. > > Application worker stops in scenario 1, seq-sync worker should also > stop. See maybe_reread_subscription(). > > We need to decide the behavior of the seq-sync worker for 2 and 3. >
Shouldn't we try to map (2) and (3) to what we do for table publication? -- With Regards, Amit Kapila.
