On 03/09/2018 11:26, pavan95 wrote:
The system expects from you to resolve the problem manually and advance the
position as needed to overcome the error.
Could you please suggest the apt measures to be followed to do the same.
Thanks in Advance.
https://www.postgresql.org/docs/10/static/logical-replication-conflicts.html
so as a first step, try to find the offending row(s) in the subscriber and then try to figure out how it was inserted there and by whom. Then delete the row or do as needed to overcome the conflict.
There should be a detail entry in the LOG file like :
[local] [70002] 5b8cf8e3.11172 2018-09-03 12:03:56.342 EEST psql postgres@dynacom line:4 DETAIL: Key (id)=(18) already exists.
That'll tell you the exact id.
If you don't want to do that because you are happier with the subscriber's version of this id, then you should advance the position.
But for starters, you better solve this by handling the row manually .
Regards,
Pavan
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
--
Achilleas Mantzios
IT DEV Lead
IT DEPT
Dynacom Tankers Mgmt
