On Tue, Jan 11, 2022 at 7:11 PM Amit Kapila <amit.kapil...@gmail.com> wrote: > > On Tue, Jan 11, 2022 at 8:52 AM Masahiko Sawada <sawada.m...@gmail.com> wrote: > > > > On Mon, Jan 10, 2022 at 8:50 PM Amit Kapila <amit.kapil...@gmail.com> wrote: > > > > > > > > > Few other comments on the latest patch: > > > ================================= > > > 1. > > > A conflict will produce an error and will stop the replication; it must be > > > resolved manually by the user. Details about the conflict can be > > > found in > > > - the subscriber's server log. > > > + <xref linkend="monitoring-pg-stat-subscription-workers"/> as well as > > > the > > > + subscriber's server log. > > > > > > Can we slightly change the modified line to: "Details about the > > > conflict can be found in <xref > > > linkend="monitoring-pg-stat-subscription-workers"/> and the > > > subscriber's server log."? > > > > Will fix it. > > > > > I think we can commit this change > > > separately as this is true even without this patch. > > > > Right. It seems an oversight of 8d74fc96db. I've attached the patch. > > > > Pushed.
Thanks! Regards, -- Masahiko Sawada EDB: https://www.enterprisedb.com/