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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/09/2018 11:56, pavan95 wrote:
Hi Team,

We have successfully configured and tested Logical Replication between
Publisher and Subscriber. But on the Subscriber side we are getting
generated a number of error log files(around 20-30 GB).

The most common log messages found in the log(/var/log/postgresql/abc.log)
are:
2018-08-26 06:32:09.659 IST [9385] ERROR:  duplicate key value violates
unique constraint "table_pkey"
2018-08-26 06:32:09.637 IST [13919] LOG:  worker process: logical
replication worker for subscription 4858103 sync 189974 (PID 9384) exited
with exit code 1
2018-08-26 06:32:09.638 IST [13919] LOG:  worker process: logical
replication worker for subscription 4858103 sync 188985 (PID 9383) exited
with exit code 1

This is severe and will eventually break your Publisher side too (the replication slot will grow forever).
So, you did something wrong, I hope - don't get me wrong I'd wish the same for myself :)
Either you created the subscription while the subscriber already had existing data in the tables, or you are inserting/updating dataI or Ds/keys on the subscriber that cause the problem .



Some 72 lakh times the above errors are occurring. How to prevent this
behaviour? Kindly assist me!!

Thanks in Advance.

Regards,
Pavan






--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html


--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt





[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux