Re: Heavy Logging in Subscriber side when configured LogicalReplication in 10.4
От | pavan95 |
---|---|
Тема | Re: Heavy Logging in Subscriber side when configured LogicalReplication in 10.4 |
Дата | |
Msg-id | 1536056608564-0.post@n3.nabble.com обсуждение исходный текст |
Ответ на | Re: Heavy Logging in Subscriber side when configured LogicalReplication in 10.4 (Achilleas Mantzios <achill@matrix.gatewaynet.com>) |
Ответы |
Re: Heavy Logging in Subscriber side when configured LogicalReplication in 10.4
Re: Heavy Logging in Subscriber side when configured LogicalReplication in 10.4 |
Список | 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
В списке pgsql-admin по дате отправления: