On Fri, Mar 4, 2022 at 9:32 PM Euler Taveira <eu...@eulerto.com> wrote: > > On Fri, Mar 4, 2022, at 2:54 AM, Amit Kapila wrote: > > The LSN of the transaction that contains the change violating the > constraint and the replication origin name can be found from the > server log (LSN 0/14C0378 and replication origin > <literal>pg_16395</literal> in the above case). To skip the > transaction, the subscription needs to be disabled temporarily by > <command>ALTER SUBSCRIPTION ... DISABLE</command> first. Then, the > transaction can be skipped by calling the <link > linkend="pg-replication-origin-advance"> > <function>pg_replication_origin_advance()</function></link> function > with the <parameter>node_name</parameter> (i.e., > <literal>pg_16395</literal>) and the next LSN of the commit LSN (i.e., > LSN 0/14C0379). > > You could also add: > > After that the replication can be resumed by <command>ALTER SUBSCRIPTION ... > ENABLE</command>. > > Let's provide complete instructions.
Thank you for the comment. +1. I've attached updated patches. Regards, -- Masahiko Sawada EDB: https://www.enterprisedb.com/
v5-0002-Add-the-origin-name-and-remote-commit-LSN-to-logi.patch
Description: Binary data
v5-0001-Use-complete-sentences-in-logical-replication-wor.patch
Description: Binary data
