From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Amit Kapila <akapila(at)postgresql(dot)org> |
Cc: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | Re: pgsql: Add ALTER SUBSCRIPTION ... SKIP. |
Date: | 2022-03-22 23:59:17 |
Message-ID: | 20220322235917.5a7exsn5fkbnx6wp@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Hi,
On 2022-03-22 01:56:03 +0000, Amit Kapila wrote:
> Add ALTER SUBSCRIPTION ... SKIP.
>
> This feature allows skipping the transaction on subscriber nodes.
>
> If incoming change violates any constraint, logical replication stops
> until it's resolved. Currently, users need to either manually resolve the
> conflict by updating a subscriber-side database or by using function
> pg_replication_origin_advance() to skip the conflicting transaction. This
> commit introduces a simpler way to skip the conflicting transactions.
>
> The user can specify LSN by ALTER SUBSCRIPTION ... SKIP (lsn = XXX),
> which allows the apply worker to skip the transaction finished at
> specified LSN. The apply worker skips all data modification changes within
> the transaction.
This was missing an include of xlogdefs.h in pg_subscription.h, thus failing
in headerscheck. See e.g.
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=crake&dt=2022-03-22%2022%3A22%3A05
I've pushed the trivial fix for that. I'll propose adding headerscheck to CI /
cfbot.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-03-23 00:08:45 | Re: pgsql: Common SQL/JSON clauses |
Previous Message | Andrew Dunstan | 2022-03-22 23:56:27 | pgsql: Revert "Common SQL/JSON clauses" |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-03-23 00:07:02 | Re: New Object Access Type hooks |
Previous Message | Andrew Dunstan | 2022-03-22 23:56:56 | Re: SQL/JSON: functions |