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 1fx8Ui-0002cu-Vg for pgsql-admin@arkaria.postgresql.org; Tue, 04 Sep 2018 10:23:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fx8Ue-0007MV-LJ for pgsql-admin@arkaria.postgresql.org; Tue, 04 Sep 2018 10:23:32 +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 1fx8Ue-0007MO-Du for pgsql-admin@lists.postgresql.org; Tue, 04 Sep 2018 10:23:32 +0000 Received: from n3.nabble.com ([162.255.23.22]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fx8Uc-0001EW-Cf for pgsql-admin@postgresql.org; Tue, 04 Sep 2018 10:23:32 +0000 Received: from n3.nabble.com (localhost [127.0.0.1]) by n3.nabble.com (Postfix) with ESMTP id 8A5BFEED87FE for ; Tue, 4 Sep 2018 03:23:28 -0700 (MST) Date: Tue, 4 Sep 2018 03:23:28 -0700 (MST) From: pavan95 To: pgsql-admin@postgresql.org Message-ID: <1536056608564-0.post@n3.nabble.com> In-Reply-To: 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> <6bb2a6ba-0425-c81c-baa9-8e56b56072df@matrix.gatewaynet.com> <1536040715349-0.post@n3.nabble.com> <771014ee-d282-f6db-911f-bfedac56c838@matrix.gatewaynet.com> <1536045135431-0.post@n3.nabble.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 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Dear Achilleas, >Start from scratch: >- drop the subscription >- truncate all tables on the subscriber side (or drop the database and recreate with --schema-only) >- recreate the subscription Done with this. Will check for any duplicate key violation errors. But have one small doubt. Think we have a table named "country" where in which 1000 records are present and it is replicated till date(all the 1000 rows are same on both publisher and subscriber). Now when an application user tries to insert another 50 records will the replication for "country" table now starts for the differential part, that is 50 records or it starts from the scratch?? How is this behaving at this juncture? Eagerly waiting for your response. Regards, Pavan -- Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html