On Tue, Nov 2, 2021 at 4:12 PM osumi.takami...@fujitsu.com <osumi.takami...@fujitsu.com> wrote: > > On Monday, June 28, 2021 1:47 PM Masahiko Sawada <sawada.m...@gmail.com> > wrote: > > On Mon, Jun 21, 2021 at 11:26 AM Mark Dilger > > <mark.dil...@enterprisedb.com> wrote: > > > > On Jun 20, 2021, at 7:17 PM, Masahiko Sawada > > <sawada.m...@gmail.com> wrote: > > > > > > > > I will submit the patch. > > > > > > Great, thanks! > > > > I've submitted the patches on that thread[1]. There are three patches: > > skipping the transaction on the subscriber side, reporting error details in > > the > > errcontext, and reporting the error details to the stats collector. > > Feedback is > > very welcome. > > > > [1] > > https://www.postgresql.org/message-id/CAD21AoBU4jGEO6AXcykQ9y7tat0R > > rB5--8ZoJgfcj%2BLPs7nFZQ%40mail.gmail.com > Hi, thanks Sawada-san for keep updating the skip xid patch in the thread. > > This thread has stopped since the patch submission. > I've rebased the 'disable_on_error' option > so that it can be applied on top of skip xid shared in [1]. > I've written Mark Dilger as the original author in the commit message. > > This patch is simply rebased to reactive this thread. > So there are still pending item to discuss for example, > how we should deal with multiple errors of several table sync workers. > > I extracted only 'disable_on_error' option > because the skip xid and the latest error message fulfill the motivation > to make it easy to write TAP tests already I felt. >
Thanks for the updated patch. Please create a Commitfest entry for this. It will help to have a look at CFBot results for the patch, also if required rebase and post a patch on top of Head. Regards, Vignesh
