| From: | "Euler Taveira" <euler(at)eulerto(dot)com> |
|---|---|
| To: | "Amit Kapila" <amit(dot)kapila16(at)gmail(dot)com>, "Masahiko Sawada" <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | "Peter Smith" <smithpb2250(at)gmail(dot)com>, "PostgreSQL Hackers" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add the replication origin name and commit-LSN to logical replication worker errcontext |
| Date: | 2022-03-04 12:32:18 |
| Message-ID: | 45c0cd68-ec87-4b2a-940e-b6ce529060c7@www.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Euler Taveira
EDB https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gilles Darold | 2022-03-04 12:35:36 | Re: [Proposal] vacuumdb --schema only |
| Previous Message | Ashutosh Sharma | 2022-03-04 12:25:08 | Re: pg_walinspect - a new extension to get raw WAL data and WAL stats |