Re: pg_logical_slot_peek_changes with slots created with pglogical_output missed DML records,

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: "James Pang (chaolpan)" <chaolpan(at)cisco(dot)com>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_logical_slot_peek_changes with slots created with pglogical_output missed DML records,
Date: 2023-01-11 06:03:02
Message-ID: CAA4eK1J89JBXfvdA6TOP_b+1UjRf-57Fx5RyQWmDo23OG8aYoQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jan 10, 2023 at 7:12 PM James Pang (chaolpan)
<chaolpan(at)cisco(dot)com> wrote:
>
> Hi,
>
> We test pglogical replication, with pglogical.conflict_resolution=error, and from source database run
>
> Insert into pgbench_branches values(109,0,’test’);
>
> Commit;
>

Can you reproduce this with native logical replication? Otherwise, it
may be better to report this on pglogical mailing list.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Adam Thomas 2023-01-11 06:04:15 pg_identify_object return missing 'domain' keyword for domain constraints
Previous Message Tom Lane 2023-01-11 00:39:06 Re: set_config with is_local parameter true escapes transaction boundaries