Re: Regarding huge logical slot lag between source and target

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: Regarding huge logical slot lag between source and target
Date: 2026-10-18 17:22:29
Message-ID: 28a109ddf0ecc56465676a878565acb29d225709.camel@cybertec.at
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, 2026-10-18 at 19:49 +0530, Durgamahesh Manne wrote:
> Logical slot lag 330GB on source grows faster during the huge modifications but it should be minimized which is not happened when load goes down.
>
> What is the action need to take for minimizing the lag to normal state.
> Source version 16
> Target version 16 
> Sufficient resources allocated and tuned replication related parameters

ALTER SUBSCRIPTION sub SET (streaming = parallel);

Also, set the following parameters to generous values (as your hardware
allows):

On the publisher:

logical_decoding_work_mem

On the subscriber:

max_logical_replication_workers
max_worker_processes
max_parallel_apply_workers_per_subscription
max_sync_workers_per_subscription

Note the dependencies: max_worker_processes must accommodate for all the
worker processes.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Durgamahesh Manne 2026-10-18 17:41:59 Re: Regarding huge logical slot lag between source and target
Previous Message Adrian Klaver 2026-10-18 15:23:55 Re: Regarding huge logical slot lag between source and target