On 1/23/25 10:21, Durgamahesh Manne wrote:
> At subscription side
> getting this error repeatedly So Do we have any solution without resync
> full data again from scratch
>
> * |2025-01-23 18:11:46 UTC::@:[507]:DEBUG: logical replication did not
> find row to be updated in replication target relation's partition
> "markets_archive_p20250118"|
That looks like a different issue.
On the subscriber side is someone/something changing the data?
Are there more log reports related to this at something above the DEBUG
level?
I'm thinking this is related to from here:
https://www.postgresql.org/docs/current/logical-replication-conflicts.html
"When replicating UPDATE or DELETE operations, missing data will not
produce a conflict and such operations will simply be skipped."
I don't have time at the moment to dig any further.
>
> Regards,
> Durga Mahesh
--
Adrian Klaver
adrian.klaver@aklaver.com
