| From: | shveta malik <shveta(dot)malik(at)gmail(dot)com> |
|---|---|
| To: | "Zhijie Hou (Fujitsu)" <houzj(dot)fnst(at)fujitsu(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Nisha Moond <nisha(dot)moond412(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, shveta malik <shveta(dot)malik(at)gmail(dot)com> |
| Subject: | Re: Conflict detection for update_deleted in logical replication |
| Date: | 2025-08-29 10:27:37 |
| Message-ID: | CAJpy0uAT+AWBuQEjj7E-zADKtZp+3uk4T9TFyqvBSoGNj_njxA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Aug 29, 2025 at 11:49 AM Zhijie Hou (Fujitsu)
<houzj(dot)fnst(at)fujitsu(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jian he | 2025-08-29 10:31:58 | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |
| Previous Message | Joel Jacobson | 2025-08-29 10:22:30 | Re: Assert single row returning SQL-standard functions |