Re: Heavy Logging in Subscriber side when configured Logical Replication in 10.4

From: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
To: pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Heavy Logging in Subscriber side when configured Logical Replication in 10.4
Date: 2018-09-04 11:30:35
Message-ID: a0512981-1014-bede-5122-3b6dc27f9f7f@matrix.gatewaynet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Dave Cramer 2018-09-04 12:40:52 Re: postgresql Logical Replication Stream fails with “Database connection failed when reading from copy”
Previous Message pavan95 2018-09-04 10:23:28 Re: Heavy Logging in Subscriber side when configured Logical Replication in 10.4