From: Amit Kapila <amit.kapila16@gmail.com>
To: James Pang (chaolpan) <chaolpan@cisco.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Subject: Re: pg_logical_slot_peek_changes with slots created with pglogical_output missed DML records,
Date: Wed, 11 Jan 2023 11:33:02 +0530
Message-ID: <CAA4eK1J89JBXfvdA6TOP_b+1UjRf-57Fx5RyQWmDo23OG8aYoQ@mail.gmail.com> (raw)
In-Reply-To: <PH0PR11MB51910EF15F24718829B4EE7DD6FF9@PH0PR11MB5191.namprd11.prod.outlook.com>
References: <PH0PR11MB51910EF15F24718829B4EE7DD6FF9@PH0PR11MB5191.namprd11.prod.outlook.com>
On Tue, Jan 10, 2023 at 7:12 PM James Pang (chaolpan)
<chaolpan@cisco.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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: amit.kapila16@gmail.com, chaolpan@cisco.com, pgsql-bugs@lists.postgresql.org
Subject: Re: pg_logical_slot_peek_changes with slots created with pglogical_output missed DML records,
In-Reply-To: <CAA4eK1J89JBXfvdA6TOP_b+1UjRf-57Fx5RyQWmDo23OG8aYoQ@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox