| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| 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 14:53:16 |
| Message-ID: | 9da3de3b-37db-444e-9bc2-2422c5840594@aklaver.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2026-10-18 15:23:55 | Re: Regarding huge logical slot lag between source and target |
| Previous Message | Durgamahesh Manne | 2026-10-18 14:19:09 | Regarding huge logical slot lag between source and target |