On Fri, Aug 29, 2025 at 11:49 AM Zhijie Hou (Fujitsu) <houzj.f...@fujitsu.com> wrote: > > Here is the new version patch set which also addressed Shveta's comments[1]. >
Thanks for the patch. On 001 alone, I’m observing a behavior where, if sub1 has stopped retention, and I then create a new subscription sub2, the worker for sub2 fails to start successfully. It repeatedly starts and exits, logging the following message: LOG: logical replication worker for subscription "sub2" will restart because the option retain_dead_tuples was enabled during startup Same things happen when I disable and re-enable 'retain_dead_tuple' of any sub once the slot has invalid xmin. thanks Shveta
