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 1fx9Xp-0006K1-CW for pgsql-admin@arkaria.postgresql.org; Tue, 04 Sep 2018 11:30:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fx9Xn-0002hv-Ic for pgsql-admin@arkaria.postgresql.org; Tue, 04 Sep 2018 11:30:51 +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 1fx9Xk-0002R6-V8 for pgsql-admin@lists.postgresql.org; Tue, 04 Sep 2018 11:30:49 +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 1fx9Xf-0002pw-DU for pgsql-admin@lists.postgresql.org; Tue, 04 Sep 2018 11:30:48 +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 w84BUaT9008355 for ; Tue, 4 Sep 2018 14:30:41 +0300 Received: from smadev.internal.net (smadev [10.9.200.131]) by smadev.internal.net (8.15.2/8.15.2) with ESMTP id w84BUaLT067736 for ; Tue, 4 Sep 2018 14:30:36 +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> <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> <1536056608564-0.post@n3.nabble.com> From: Achilleas Mantzios Message-ID: Date: Tue, 4 Sep 2018 14:30:35 +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: <1536056608564-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 04/09/2018 13:23, pavan95 wrote: > 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. From the deferential part. It will replicate from the last successful position onward. It is all in the docs. > > Regards, > Pavan > > > > -- > Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html > -- Achilleas Mantzios IT DEV Lead IT DEPT Dynacom Tankers Mgmt