From: Achilleas Mantzios <achill@matrix.gatewaynet.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Heavy Logging in Subscriber side when configured Logical Replication in 10.4
Date: Mon, 3 Sep 2018 12:05:57 +0300
Message-ID: <6bb2a6ba-0425-c81c-baa9-8e56b56072df@matrix.gatewaynet.com> (raw)
In-Reply-To: <1535963171985-0.post@n3.nabble.com>
References: <1535792170623-0.post@n3.nabble.com>
<5b79452e-cec6-c93c-76de-968be43be45e@matrix.gatewaynet.com>
<1535961028810-0.post@n3.nabble.com>
<ba731059-dfd7-2d34-b3a5-83a20b564a1d@matrix.gatewaynet.com>
<1535963171985-0.post@n3.nabble.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: achill@matrix.gatewaynet.com, pgsql-admin@lists.postgresql.org
Subject: Re: Heavy Logging in Subscriber side when configured Logical Replication in 10.4
In-Reply-To: <6bb2a6ba-0425-c81c-baa9-8e56b56072df@matrix.gatewaynet.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox