| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Records count mismatch with logical replication |
| Date: | 2025-01-23 18:38:31 |
| Message-ID: | 6ac2ce9c-5be6-4e6a-abef-b3dc72f96121@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Saul Perdomo | 2025-01-23 19:02:12 | Re: Return of the pg_wal issue.. |
| Previous Message | Adrian Klaver | 2025-01-23 18:28:22 | Re: Records count mismatch with logical replication |