From: pavan95 <pavan.postgresdba@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: Can we exclude errors of some particular text in Postgres log file?
Date: Sun, 2 Sep 2018 22:27:39 -0700 (MST)
Message-ID: <1535952459485-0.post@n3.nabble.com> (raw)
In-Reply-To: <CAHw75vsYG8XM=Peg0Pz17dacDKgdSRhPq0p0kyy8bpGuHNzeTg@mail.gmail.com>
References: <1535796881126-0.post@n3.nabble.com>
<CAHw75vsYG8XM=Peg0Pz17dacDKgdSRhPq0p0kyy8bpGuHNzeTg@mail.gmail.com>
Hi Keith,
I'm getting this error due to logical replication configured. And this error
is occurring on the Subscriber Side.
In my point of view, Logical Replication worker process is continuously
checking and trying to insert each row right from the start even if that
particular row has been already present in the table. And that's the reason
of this continuous occurring of the error.
One small doubt is if a table A has 10 records(which were inserted on the
publisher) and all the 10 records were replicated to the subscriber. Now
when I insert the 11'th record will it replicate only the last record or try
to replicate(or check if all rows have been replicated) all the rows of the
table A right from the first?? Please confirm..
If it does the latter(try to replicate all rows) then the above error will
arise as table A has replica identity(Primary key).
>>If this doesn't fit the model that is causing your duplicate key errors,
you may want to look into using a function to do your writes instead and
catch the given error in an exception block and then just ignore it.
Could you please provide me an example of accomplishing it!!
Thanks in Advance.
Regards,
Pavan
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html
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: pavan.postgresdba@gmail.com
Subject: Re: Can we exclude errors of some particular text in Postgres log file?
In-Reply-To: <1535952459485-0.post@n3.nabble.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