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 11:04:04 +0300
Message-ID: <ba731059-dfd7-2d34-b3a5-83a20b564a1d@matrix.gatewaynet.com> (raw)
In-Reply-To: <1535961028810-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>
On 03/09/2018 10:50, pavan95 wrote:
> Hi Achilleas,
>
> But the logical Replication is working fine. I mean to say that the data is
> replicating between Publisher and Subscriber. I have problem only with my
> logs. Most common errors found on my Subscriber are:
>
> 1. duplicate key value violates unique constraint
> 2. worker process: logical replication worker for subscription 6992680 sync
> 694478 (PID 13459) exited with exit code 1
> 3. logical replication table synchronization worker for subscription
> ""subscription_name"", table ""tbl_A"" has started
>
>>> 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 .
>
> Even if I did that it will face this error the very first time it is trying
> to establish sync between publisher and subscriber but not every
> time(correct me if I am wrong)
it will go like this forever.
So you must try to find the offending rows on both sides and explain how did it happen.
I repeat, this is serious, and not supposed to happen.
The system expects from you to resolve the problem manually and advance the position as needed to overcome the error.
Until you do this, you'll keep getting this ERROR.
Read the docs.
>
> The 2'nd & 3'rd are not actually ERRORS. They are LOG messages. Please
> suggest me if I went wrong somewhere.
>
>
>
> --
> 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: <ba731059-dfd7-2d34-b3a5-83a20b564a1d@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