Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1taK7N-000njE-Q4 for pgsql-general@arkaria.postgresql.org; Tue, 21 Jan 2025 19:40:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1taK7M-004c0P-2F for pgsql-general@arkaria.postgresql.org; Tue, 21 Jan 2025 19:40:56 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1taK7L-004bvJ-Kx for pgsql-general@lists.postgresql.org; Tue, 21 Jan 2025 19:40:55 +0000 Received: from mail-ej1-x62f.google.com ([2a00:1450:4864:20::62f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1taK7J-000mXV-0f for pgsql-general@lists.postgresql.org; Tue, 21 Jan 2025 19:40:54 +0000 Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-aaef00ab172so918736166b.3 for ; Tue, 21 Jan 2025 11:40:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1737488452; x=1738093252; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=AEWb8GRpYi4NOklvm2zDSR7VnnGHsE8vUss7fZKOZp0=; b=mS0VUsiXAvc+1lINkHsmECL5QcqE/mYKHlBfuiJbVUVeVf+hBRGwh42NJq38Gitssp vrYePBDzzAmFugNg6ZTW7Umh568+cym66aHxB3jqWn0HnfYy37ZrM0/m7cukX5ILyYxx f1YE29O4I0+PODGtwHmQwAoA7hiy+mkNqdZC2CQqcL4oQqLmcohxld6IGhvuONcHc2Ju h/snVkf/b//yTGrRr/g+Ow+OpnsA6isp9GL24B3b6AY90N6DZaC6fADFy+JGNx6xjp/M Jhs7UMyj8tP166z+tOzZ4WpeEu0BoOSs0pxTS9ZQpOjUyrVLNDC9qWZ8XbW8WLQKgNEH f4DQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737488452; x=1738093252; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=AEWb8GRpYi4NOklvm2zDSR7VnnGHsE8vUss7fZKOZp0=; b=t5C3kkrElGUHu6BCF2MAKKYRGZs9IQS+PRanLyknjvhrSL/vg8s8duEqttv2b8h4jr gwsGTqt4cB6Tke6ormzRDUcIfOg6jZfMO6aWmEdJurUYs7A31WE8svuQR7WC4wrz2IXO y+kJuLUeInxgyH1tR+V8dwG6GNPDSwYu6JDZEJmORy8rcwyYG/F+9Rth9aO2540ISELr h+pGzOphvW9OO7dSeXqverDoMmPFFxg9uYpItu+gIEbiM4UIk3A+ljMyubtiLxzR2Sp2 QE/1jRm9aiUIAL2uqfLbsMU7o3hz3F0ZjZWYRKGJHkspo/P2qqf/wtUv54Rgc2uvijwn N3TA== X-Gm-Message-State: AOJu0YwgFswwqf2ZdzUyoFcVjJlRd8BKfOqbXOqtST1z/shcyYv90xR0 GC/w6dY03yQyrmi8C7lxCVwxhEOZcOJFae0KwLJpTD5ZizeHc1MhfRpoddGw/ApjwWa45LXHApS LBJCs12FMcyE6XKADayjBT/64KHG3XujP7Mo= X-Gm-Gg: ASbGnctkyYlDnfkuXK1dRKNjQfZdWFsz3eQdrc8TY0Ss2N/uKFvTXJTKiRV4Pihx0c+ I1gHl5e0uJGgjUQA6WthHzWVT7cRdEHca+ojXmdM5vSxJbUPz3s2n X-Google-Smtp-Source: AGHT+IELqf095KpW8GhlLKA7d2mspoWJlcCLhQ/BjGT4/Uxz6uaAuGpJdCuTijKDXXvptG3wwx7uu+df46oVaXcroLw= X-Received: by 2002:a05:6402:1e8e:b0:5d4:55e:f99e with SMTP id 4fb4d7f45d1cf-5db7d300e9dmr43990600a12.18.1737488451860; Tue, 21 Jan 2025 11:40:51 -0800 (PST) MIME-Version: 1.0 References: <79b7d5dc-3a1d-4ef0-9a3d-055268dc7d09@aklaver.com> <3691ad0c-189c-4290-a434-e03cb6301cac@aklaver.com> In-Reply-To: <3691ad0c-189c-4290-a434-e03cb6301cac@aklaver.com> From: Durgamahesh Manne Date: Wed, 22 Jan 2025 01:10:34 +0530 X-Gm-Features: AbW1kvb8yafhigEDOx-dCdE3apiZ2munI9gWo6iePBu093d2eZjcprmYgaeS79E Message-ID: Subject: Re: Records count mismatch with logical replication To: Adrian Klaver Cc: pgsql-general Content-Type: multipart/alternative; boundary="000000000000f97ee0062c3c8d26" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000f97ee0062c3c8d26 Content-Type: text/plain; charset="UTF-8" On Wed, 22 Jan, 2025, 00:22 Adrian Klaver, wrote: > > > On 1/21/25 10:06 AM, Durgamahesh Manne wrote: > > > > > Hi Adrian Klaver > > > > 22,906,216 bytes/10,846 rows works out to 2112 bytes per row. > > > > Is that a reasonable per row estimate? > > > > Yes sometimes would be vary > > If I am following the lag went from 350GB behind to 22MB. > > Is the issue that the lag has stalled at 22MB? > > > > > Regards, > > Durga Mahesh > > > > -- > Adrian Klaver > adrian.klaver@aklaver.com Hi Adrian Klaver Is the issue that the lag has stalled at 22MB? Depends on load of source The lag would be either decrease or increase in Kb 's and Mb's (not Gb's) It s not constant as Data being replicated to target But records count varies with difference of more than 10 thousand How to mitigate this issue in simplest way ? Regards Durga Mahesh --000000000000f97ee0062c3c8d26 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Wed, 22 Jan, 2025, 00:22 Adri= an Klaver, <adrian.klaver@a= klaver.com> wrote:


On 1/21/25 10:06 AM, Durgamahesh Manne wrote:

>
> Hi Adrian Klaver
>
> 22,906,216 bytes/10,846 rows=C2=A0 works out to 2112 bytes per row. >
> Is that a reasonable per row estimate?
>
> Yes=C2=A0 sometimes would be vary

If I am following the lag went from 350GB behind to 22MB.

Is the issue that the lag has stalled at 22MB?

>
> Regards,
> Durga Mahesh
>

--
Adrian Klaver
adrian.klaver@aklaver.com

Hi Adrian Klaver
Is the issue that the lag has stalled at 22MB?

Depends on load of source= =C2=A0
The lag would be either decrease or increase = in Kb 's and Mb's (not Gb's)
It s not co= nstant as Data being replicated to target

=
But records count varies with difference of more than 10 = thousand=C2=A0

How to mi= tigate this issue in simplest way ?

Regards=C2=A0
Durga Mahesh=C2=A0
--000000000000f97ee0062c3c8d26--