Re: Regarding huge logical slot lag between source and target

On 10/18/26 8:08 AM, Durgamahesh Manne wrote:

When you reply, also include the mailing list. In other words Reply All.

Ccing list.

Also copy and paste information in screenshot as it did not make it into
this reply.
More comments in line.
>
>
> On Sun, 18 Oct, 2026, 20:23 Adrian Klaver, <adrian(dot)klaver(at)aklaver(dot)com

> Hi
>
> Both are in same data center.
>
> Source 128gb ram and 32 vcpus
> Target  128gb ram and  64 vcpus
>
> Source params
> Logical decoding work mem 4gB
> Max replication slots 20
> Max wal senders 35
> Max worker processes 64
> Wal keep size 48gb
> Wal level logical
> Wal sender timeout 30min
> Min wal size 16gb
> Max wal size 64gb
>
> Target params
> Min wal size 24gb
> Max worker processes 80
> Max wal size 90gb
> Wal keep size 55gb not required at target
> Max logical replication workers 50
> Max parallel workers 12
>
>
> Already set subscription with streaming and binary

Between same two machines?

Why multiple forms of replication?

>
> Huge updates on one table

Again define what a huge update is, 100,000 rows and 1,000,000 rows or
something else?

> Please what attributes needed from replication slots and stat
> replication tables .
>
>
>
> See here 3rd slot lag
>
>
> Regards
> Durga Mahesh
>
>

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com