| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Durgamahesh Manne <maheshpostgres9(at)gmail(dot)com> |
| Cc: | 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 18:43:46 |
| Message-ID: | 93db43ba32753c2197a8e8a9253924342f633a48.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sun, 2026-10-18 at 23:11 +0530, Durgamahesh Manne wrote:
> On Sun, 18 Oct, 2026, 22:52 Laurenz Albe, <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> > 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
> >
> > [I suggested "streaming = parallel" and increasing some parameters}
>
> I already set those params with required values to make server running smoothly
>
> Alter subscription also done with binary and streaming options
>
> Finally I could not find root cause what has caused to increase of that much lag.
>
> No long running queries at source
> No blocking at target
> Generally what might be reason to huge lag in terms of hundreds which can't go down.
Perhaps DDL statements on the publisher.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2026-10-18 18:45:25 | Re: Regarding huge logical slot lag between source and target |
| Previous Message | Durgamahesh Manne | 2026-10-18 17:46:03 | Re: Regarding huge logical slot lag between source and target |