On Fri, May 28, 2021 at 12:31 PM tanghy.fnst@fujitsu.com
<tanghy.fnst@fujitsu.com> wrote:
>
> On Friday, May 28, 2021 3:02 PM, tanghy.fnst@fujitsu.com wrote:
> > FYI. The problem also occurs in PG-13. I will try to check from which version it
> > got introduced.
>
> I reproduced it in PG-10,11,12,13.
> I think the problem has been existing since Logical replication introduced in PG-10.
Seems you did not set the replica identity for updating the tuple.
Try this before updating, and it should work.
ALTER TABLE toasted_key REPLICA IDENTITY USING INDEX toasted_key_pkey;
or
ALTER TABLE toasted_key REPLICA IDENTITY FULL.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
