pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Adrian Klaver <adrian.klaver@aklaver.com>
To: Durgamahesh Manne <maheshpostgres9@gmail.com>
To: pgsql-general <pgsql-general@lists.postgresql.org>
To: PostgreSQL mailing lists <pgsql-general@postgresql.org>
Subject: Re: Regarding huge logical slot lag between source and target
Date: Sun, 18 Oct 2026 07:53:16 -0700
Message-ID: <9da3de3b-37db-444e-9bc2-2422c5840594@aklaver.com> (raw)
In-Reply-To: <CAJCZkoKxTLGZfYu0uT6ihZe0dPzqcjeA-TKWkgDEhaFAadhVew@mail.gmail.com>
References: <CAJCZkoKxTLGZfYu0uT6ihZe0dPzqcjeA-TKWkgDEhaFAadhVew@mail.gmail.com>

On 10/18/26 7:19 AM, Durgamahesh Manne wrote:
> Hi
> 
> 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 does the number 330 GB represent?

Define 'huge modifications'.

Give numbers under load and when load is reduced.

> 
> What is the action need to take for minimizing the lag to normal state.
> Source version 16
> Target version 16

Where are the source and target located relative to each other:
    Same machine.
    Same data center.
    Different data centers.  If so what is the network distance?


> Sufficient resources allocated and tuned replication related parameters

Given your opening sentence it looks like you do not have 'Sufficient 
resources'.

Provide the numbers for resources and replication parameters.


> 
> 
> Regards
> Durga Mahesh
> 


-- 
Adrian Klaver
adrian.klaver@aklaver.com






view thread (19+ messages)  latest in thread

Message-ID: <9da3de3b-37db-444e-9bc2-2422c5840594@aklaver.com>
Permalink:  ../9da3de3b-37db-444e-9bc2-2422c5840594@aklaver.com/
Also on:    postgresql.org/message-id/9da3de3b-37db-444e-9bc2-2422c5840594@aklaver.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: adrian.klaver@aklaver.com, maheshpostgres9@gmail.com
  Subject: Re: Regarding huge logical slot lag between source and target
  In-Reply-To: <9da3de3b-37db-444e-9bc2-2422c5840594@aklaver.com>
  References: <CAJCZkoKxTLGZfYu0uT6ihZe0dPzqcjeA-TKWkgDEhaFAadhVew@mail.gmail.com> <9da3de3b-37db-444e-9bc2-2422c5840594@aklaver.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox