On Mon, May 31, 2021 at 12:20 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> On Mon, May 31, 2021 at 8:04 AM tanghy.fnst@fujitsu.com
> <tanghy.fnst@fujitsu.com> wrote:
> >
> > On Friday, May 28, 2021 6:51 PM, Dilip Kumar <dilipbalaut@gmail.com> wrote:
> > > Seems you did not set the replica identity for updating the tuple.
> > > Try this before updating, and it should work.
> >
> > Thanks for your reply. I tried it.
> >
> > > ALTER TABLE toasted_key REPLICA IDENTITY USING INDEX toasted_key_pkey;
> >
> > This didn't work.
> >
> > > or
> > >
> > > ALTER TABLE toasted_key REPLICA IDENTITY FULL.
> >
> > It worked.
> >
> > And I noticed if the length of PRIMARY KEY (toasted_key) is short, data could be synchronized successfully with
defaultreplica identity.
> > Could you tell me why we need to set replica identity?
>
> Looks like some problem if the replica identity is an index and the
> value is stored externally, I will debug this and let you know.
The problem is if the key attribute is not changed we don't log it as
it should get logged along with the updated tuple, but if it is
externally stored then the complete key will never be logged because
there is no log from the toast table. For fixing this if the key is
externally stored then always log that.
Please test with the attached patch.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com