From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | pavan95 <pavan(dot)postgresdba(at)gmail(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Heavy Logging in Subscriber side when configured Logical Replication in 10.4 |
Date: | 2018-09-04 06:12:54 |
Message-ID: | CAKFQuwbW+XQSHV1=McXB2UM9_MaBVj4C+gg7-JSpQTO7RpSQ=Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
On Monday, September 3, 2018, pavan95 <pavan(dot)postgresdba(at)gmail(dot)com> wrote:
> Hi Achilleas,
>
> >>>Either you created the subscription while the subscriber already had
> existing data in the tables
>
> I had taken a backup(along with data) and restored on both publisher and
> subscriber. Later which I have created Publication and Subscription on both
> the nodes.
>
I don’t know if this can be made to function properly but it’s definitely
not the expected usage pattern.
Expected is that one node publishes and the other one subscribes. The
subscriber starts from scratch and synchronizes from the publisher.
Lacking any more specific responses you should consider dropping
(truncating?) the relevant tables and subscription from the subscriber node
and starting from scratch so as to conform to the expected usage pattern.
Have not used the feature myself so can’t be of much more help than this...
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Achilleas Mantzios | 2018-09-04 06:32:27 | Re: Heavy Logging in Subscriber side when configured Logical Replication in 10.4 |
Previous Message | pavan95 | 2018-09-04 05:58:35 | Re: Heavy Logging in Subscriber side when configured Logical Replication in 10.4 |