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 1fwkoR-0003vy-HQ for pgsql-admin@arkaria.postgresql.org; Mon, 03 Sep 2018 09:06:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fwkoP-0007Tq-Jm for pgsql-admin@arkaria.postgresql.org; Mon, 03 Sep 2018 09:06:21 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fwkoP-0007Ti-9E for pgsql-admin@lists.postgresql.org; Mon, 03 Sep 2018 09:06:21 +0000 Received: from hermes.gatewaynet.com ([193.92.121.98]) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1fwkoK-0008HN-To for pgsql-admin@lists.postgresql.org; Mon, 03 Sep 2018 09:06:20 +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 w8395wrA002440 for ; Mon, 3 Sep 2018 12:06:03 +0300 Received: from smadev.internal.net (smadev [10.9.200.131]) by smadev.internal.net (8.15.2/8.15.2) with ESMTP id w8395vp9070118 for ; Mon, 3 Sep 2018 12:05:58 +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> <5b79452e-cec6-c93c-76de-968be43be45e@matrix.gatewaynet.com> <1535961028810-0.post@n3.nabble.com> <1535963171985-0.post@n3.nabble.com> From: Achilleas Mantzios Message-ID: <6bb2a6ba-0425-c81c-baa9-8e56b56072df@matrix.gatewaynet.com> Date: Mon, 3 Sep 2018 12:05:57 +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: <1535963171985-0.post@n3.nabble.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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 03/09/2018 11:26, pavan95 wrote: >>> The system expects from you to resolve the problem manually and advance the > position as needed to overcome the error. > > Could you please suggest the apt measures to be followed to do the same. > Thanks in Advance. https://www.postgresql.org/docs/10/static/logical-replication-conflicts.html so as a first step, try to find the offending row(s) in the subscriber and then try to figure out how it was inserted there and by whom. Then delete the row or do as needed to overcome the conflict. There should be a detail entry in the LOG file like : [local] [70002] 5b8cf8e3.11172 2018-09-03 12:03:56.342 EEST psql postgres@dynacom line:4 DETAIL:  Key (id)=(18) already exists. That'll tell you the exact id. If you don't want to do that because you are happier with the subscriber's version of this id, then you should advance the position. But for starters, you better solve this by handling the row manually . > > > Regards, > Pavan > > > > -- > Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html > -- Achilleas Mantzios IT DEV Lead IT DEPT Dynacom Tankers Mgmt