Re: Skipping logical replication transactions on subscriber side

On Tue, Aug 17, 2021 at 5:21 PM tanghy(dot)fnst(at)fujitsu(dot)com
<tanghy(dot)fnst(at)fujitsu(dot)com> wrote:
>
> On Thursday, August 12, 2021 1:53 PM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> >
> > I've attached the updated patches. FYI I've included the patch
> > (v8-0005) that fixes the assertion failure during shared fileset
> > cleanup to make cfbot tests happy.
>
>
> Hi
>
> Thanks for your patch. I met a problem when using it. The log is not what I expected in some cases, but in streaming mode, they work well.
>
> For example:
> ------publisher------
> create table test (a int primary key, b varchar);
> create publication pub for table test;
>
> ------subscriber------
> create table test (a int primary key, b varchar);
> insert into test values (10000);
> create subscription sub connection 'dbname=postgres port=5432' publication pub with(streaming=on);
>
> ------publisher------
> insert into test values (10000);
>
> Subscriber log:
> 2021-08-17 14:24:43.415 CST [3630341] ERROR: duplicate key value violates unique constraint "test_pkey"
> 2021-08-17 14:24:43.415 CST [3630341] DETAIL: Key (a)=(10000) already exists.
>
> It didn't give more context info generated by apply_error_callback function.

Thank you for reporting the issue! This issue must be fixed in the
latest (v9) patches I've just submitted[1].

Regards,

[1] https://www.postgresql.org/message-id/CAD21AoCH4Jwn_NkJhvS6W5bZJKSaAYnC9inXqMJc6dLLvhvTQg%40mail.gmail.com

--
Masahiko Sawada
EDB: https://www.enterprisedb.com/