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 1fx5Vi-0000Rp-0l for pgsql-admin@arkaria.postgresql.org; Tue, 04 Sep 2018 07:12:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fx5Vd-00029M-9O for pgsql-admin@arkaria.postgresql.org; Tue, 04 Sep 2018 07:12:21 +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 1fx5Vd-00029E-1r for pgsql-admin@lists.postgresql.org; Tue, 04 Sep 2018 07:12:21 +0000 Received: from n3.nabble.com ([162.255.23.22]) by magus.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fx5VZ-00053C-R9 for pgsql-admin@postgresql.org; Tue, 04 Sep 2018 07:12:20 +0000 Received: from n3.nabble.com (localhost [127.0.0.1]) by n3.nabble.com (Postfix) with ESMTP id 73A71EEC91AC for ; Tue, 4 Sep 2018 00:12:15 -0700 (MST) Date: Tue, 4 Sep 2018 00:12:15 -0700 (MST) From: pavan95 To: pgsql-admin@postgresql.org Message-ID: <1536045135431-0.post@n3.nabble.com> In-Reply-To: <771014ee-d282-f6db-911f-bfedac56c838@matrix.gatewaynet.com> 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> 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 Hi Achilleas/David, So like what you have said, making the subscriber table structure(only) ready will sort out this issue? If yes, I will drop the existing replication and start from the scratch. Or else like what David had suggested is truncating all the tables sufficient?? Please confirm. Looking forward to hear from you!!. Finding my way interesting in this logical replication. And thanks team for your wonderful support. Regards, Pavan -- Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html