From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | Kacey Holston <kacey(dot)holston(at)pgexperts(dot)com> |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Issue with logical replication |
Date: | 2021-08-10 04:21:12 |
Message-ID: | CAA4eK1+7TUDGT+NTmdOVNHdp_dpScDT-MeACjPoDt5ZcqpSkNg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Aug 10, 2021 at 12:25 AM Kacey Holston
<kacey(dot)holston(at)pgexperts(dot)com> wrote:
>
> My apologies.
>
> The data was missing on PG13 from the initial copy.
>
Okay, so all the steps after you say "We then reversed the direction
of replication by running this on the PostgreSQL 13 server:" in your
email are not required to see the problem, right?
Can you please tell whether the data you see missing is the new data
generated on the publisher when the copy is in progress or it was the
original data of the table? Please tell me the situation when you have
used Create Subscription command *not* when you were using manually
created slot. Also, do you have any subscriber/publisher side logs
during that time which you can share?
Note - Please respond to the email in-line as it is easier to
communicate that way and that is the style we use to discuss here.
--
With Regards,
Amit Kapila.
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2021-08-10 06:15:27 | Re: I/O timigns don't include time for temp buffers |
Previous Message | David G. Johnston | 2021-08-10 03:17:59 | Re: information_schema.constraint_column_usage shows wrong table name |