Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fwj3w-0006Sc-82 for pgsql-admin@arkaria.postgresql.org; Mon, 03 Sep 2018 07:14:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fwj3r-0001Hw-6V for pgsql-admin@arkaria.postgresql.org; Mon, 03 Sep 2018 07:14:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fwj3q-0001Hp-VU for pgsql-admin@lists.postgresql.org; Mon, 03 Sep 2018 07:14:11 +0000 Received: from hermes.gatewaynet.com ([193.92.121.98]) by magus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fwj3o-0005GC-7j for pgsql-admin@lists.postgresql.org; Mon, 03 Sep 2018 07:14:10 +0000 Received: from smadev.internal.net (pc131.internal.net [10.9.200.131]) by hermes.gatewaynet.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id w837Dlel004460 for ; Mon, 3 Sep 2018 10:13:52 +0300 Received: from smadev.internal.net (smadev [10.9.200.131]) by smadev.internal.net (8.15.2/8.15.2) with ESMTP id w837DlI7063795 for ; Mon, 3 Sep 2018 10:13:47 +0300 (EEST) (envelope-from achill@matrix.gatewaynet.com) Subject: Re: Heavy Logging in Subscriber side when configured Logical Replication in 10.4 To: pgsql-admin@lists.postgresql.org References: <1535792170623-0.post@n3.nabble.com> From: Achilleas Mantzios Message-ID: <5b79452e-cec6-c93c-76de-968be43be45e@matrix.gatewaynet.com> Date: Mon, 3 Sep 2018 10:13:47 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <1535792170623-0.post@n3.nabble.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Virus-Scanned: clamav-milter 0.98.7 at hermes X-Virus-Status: Clean X-Spam-Status: No, score=-27.0 required=5.0 tests=ALL_TRUSTED,DYN_HAM_COORD, DYN_HAM_IT,DYN_HAM_NAUTICAL,DYN_HAM_SIGNAT1,DYN_SPAM_MED6 autolearn=unavailable version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on hermes.gatewaynet.com List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 01/09/2018 11:56, pavan95 wrote: > Hi Team, > > We have successfully configured and tested Logical Replication between > Publisher and Subscriber. But on the Subscriber side we are getting > generated a number of error log files(around 20-30 GB). > > The most common log messages found in the log(/var/log/postgresql/abc.log) > are: > 2018-08-26 06:32:09.659 IST [9385] ERROR: duplicate key value violates > unique constraint "table_pkey" > 2018-08-26 06:32:09.637 IST [13919] LOG: worker process: logical > replication worker for subscription 4858103 sync 189974 (PID 9384) exited > with exit code 1 > 2018-08-26 06:32:09.638 IST [13919] LOG: worker process: logical > replication worker for subscription 4858103 sync 188985 (PID 9383) exited > with exit code 1 This is severe and will eventually break your Publisher side too (the replication slot will grow forever). So, you did something wrong, I hope - don't get me wrong I'd wish the same for myself :) Either you created the subscription while the subscriber already had existing data in the tables, or you are inserting/updating dataI or Ds/keys on the subscriber that cause the problem . > > > Some 72 lakh times the above errors are occurring. How to prevent this > behaviour? Kindly assist me!! > > Thanks in Advance. > > Regards, > Pavan > > > > > > > -- > Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html > -- Achilleas Mantzios IT DEV Lead IT DEPT Dynacom Tankers Mgmt