|
There are multiple ways to deal with this . Also you have not mentioned the nature of the environment .
Check the Postgres log file , at the server where you are getting this primary key violation error . Along with error message it should print the error value as well . Take the same value and verify at table .
Another way to handle the scenario (considering it as production / client side environment) , take the table dump , using pgdump from each DB server . Restore those 2 dump into 2 different tabel , in some different server . After that that you can easily
find out the duplicate key value by query .
Hope this will resolve your issue .
Thanks ,
Soumitra
From: pavan95 <pavan.postgresdba@xxxxxxxxx>
Sent: Monday, September 3, 2018 11:33 AM To: pgsql-admin@xxxxxxxxxxxxxx Subject: Re: Heavy Logging in Subscriber side when configured Logical Replication in 10.4 Hi Soumitra,
Thanks for your timely response. >>This may be due to several reason , so you have to remove that conflict first . Could you suggest me a way to do it. I am unable to figure out why this data integrity came into picture(like why it is failing). In order to reduce this what are measures to cope with?? Thanks in Advance. Regards, Pavan -- Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html |
