| From: | pavan95 <pavan(dot)postgresdba(at)gmail(dot)com> |
|---|---|
| To: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Heavy Logging in Subscriber side when configured Logical Replication in 10.4 |
| Date: | 2018-09-04 10:23:28 |
| Message-ID: | 1536056608564-0.post@n3.nabble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Achilleas Mantzios | 2018-09-04 11:30:35 | Re: Heavy Logging in Subscriber side when configured Logical Replication in 10.4 |
| Previous Message | Praneel Devisetty | 2018-09-04 07:48:52 | User to get locked after three wrong login attempts. |