Feedback-ID: i76984098:Fastmail
Message-ID: <6ac2ce9c-5be6-4e6a-abef-b3dc72f96121@aklaver.com>
Date: Thu, 23 Jan 2025 10:38:31 -0800
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Records count mismatch with logical replication
To: Durgamahesh Manne <maheshpostgres9@gmail.com>
Cc: pgsql-general <pgsql-general@lists.postgresql.org>
References: <CAJCZko+gYNGiixGcqKAhjhLhUZ3QQg2rGs6nH7ZUNwTtjYLfGw@mail.gmail.com>
 <e1bd37c2-9e2c-4914-b8be-bd75b633dfc1@aklaver.com>
 <CAJCZko+HhLFkiDLDPg3fscUEO4uWyEFT4_e6GBMeywnnwRC-rg@mail.gmail.com>
 <79b7d5dc-3a1d-4ef0-9a3d-055268dc7d09@aklaver.com>
 <CAJCZkoLZb5ON_T-YecS3-1sQjiGUVLdgKjS93thQyzZKiaWuFQ@mail.gmail.com>
 <3691ad0c-189c-4290-a434-e03cb6301cac@aklaver.com>
 <CAJCZkoJgAh_T_NJU5Jn3mzJJQE4LE-tDEjEyP37gKNR1X0cDWQ@mail.gmail.com>
 <44e3ca5d-fcbd-4f96-a6a6-09becff15cd7@aklaver.com>
 <CAJCZkoLatfwsQ-puesPfjrYtUmaAwokWQvqShoTGfJ56QzLfQw@mail.gmail.com>
 <aa3168eb-f529-4e4a-bcb7-e01140ef5b3f@aklaver.com>
 <CAJCZkoKvzBxjAZxfOsUpEmwmrtV33ZZaHC-d-yvF6RPAxoATkQ@mail.gmail.com>
 <CAJCZkoJrrezxCHxh0tmy-LQ+6CeizkDt88kM_yTDzVADhLdsJQ@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAJCZkoJrrezxCHxh0tmy-LQ+6CeizkDt88kM_yTDzVADhLdsJQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/6ac2ce9c-5be6-4e6a-abef-b3dc72f96121%40aklaver.com>
Precedence: bulk

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