Date: Sun, 2 Sep 2018 23:28:34 -0700 (MST)
From: pavan95 <pavan.postgresdba@gmail.com>
To: pgsql-admin@postgresql.org
Message-ID: <1535956114648-0.post@n3.nabble.com>
In-Reply-To: 
 <MA1PR0101MB1687B5878714AA511B9E3697E00C0@MA1PR0101MB1687.INDPRD01.PROD.OUTLOOK.COM>
References: <1535792170623-0.post@n3.nabble.com>
 <1535952517864-0.post@n3.nabble.com>
 <MA1PR0101MB1687E0C4823BB4A9C430C7FCE00C0@MA1PR0101MB1687.INDPRD01.PROD.OUTLOOK.COM>
 <1535954598462-0.post@n3.nabble.com>
 <MA1PR0101MB1687B5878714AA511B9E3697E00C0@MA1PR0101MB1687.INDPRD01.PROD.OUTLOOK.COM>
Subject: Re: Heavy Logging in Subscriber side when configured Logical
 Replication in 10.4
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi Soumitra,

Actually speaking there is no duplicacy of the records. This error is
occurring on the subscriber side of the logical replication.

And the data on publisher is same as the data in subscriber. So there is no
point of mismatch in data integrity. 

And I think this error is caused because logical replication worker is
trying the sync the already synced rows from publisher to subscriber. In a
day it is occurring approximately 5264718 times.

This is causing heavy logging at the subscriber. I think you got my problem.

Environment:

The environment is two ubuntu boxes configured with Logical Replication on
Postgres 10.4. And the error flooding is occurring on the subscriber side.
Thanks in Advance.

Regards,
Pavan


--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html