MIME-Version: 1.0
References: <CAG-eXHKr5pFzCKNqVhjQAUM0oxxCe8YUfjoLT8WmZx54Sk48kg@mail.gmail.com>
In-Reply-To: <CAG-eXHKr5pFzCKNqVhjQAUM0oxxCe8YUfjoLT8WmZx54Sk48kg@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Wed, 25 Sep 2024 10:42:07 -0400
Message-ID: <CAKAnmmLmvuo=TORx=hDw2y5fFOUc0sHb88O+6Z-Cs=oVtN9W4A@mail.gmail.com>
Subject: Re: Logical Replication Delay
To: Ramakrishna m <ram.pgdb@gmail.com>
Cc: pgsql-general@lists.postgresql.org, ravisql09@gmail.com
Content-Type: multipart/alternative; boundary="00000000000097166d0622f2a24e"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmmLmvuo%3DTORx%3DhDw2y5fFOUc0sHb88O%2B6Z-Cs%3DoVtN9W4A%40mail.gmail.com>
Precedence: bulk

--00000000000097166d0622f2a24e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Sat, Sep 21, 2024 at 3:08=E2=80=AFPM Ramakrishna m <ram.pgdb@gmail.com> =
wrote:

> I would greatly appreciate any suggestions you may have to help avoid
> logical replication delays, whether through tuning database or operating
> system parameters, or any other recommendations
>
In addition to the things already answered:

* What is the use case for logical replication? I assume your local
replicas are able to keep up just fine.

* Check the nature of the work for problems, e.g. ORM doing
unnecessary/redundant updates, maintaining indexes that are not really
needed

* Looks like your wal_segment_size was boosted to 1GB. What drove that
change?

* Yes, autovacuum could affect things - make sure
log_autovacuum_min_durations is set

Cheers,
Greg

--00000000000097166d0622f2a24e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Sat, Sep 21, 2024 at 3:08=E2=80=AFPM R=
amakrishna m &lt;<a href=3D"mailto:ram.pgdb@gmail.com">ram.pgdb@gmail.com</=
a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><div dir=3D"ltr"><p></p><p><span style=3D"color:rg=
b(0,0,0);font-family:arial,sans-serif">I would greatly appreciate any sugge=
stions you may have to help avoid logical replication delays, whether throu=
gh tuning database or operating system parameters, or any other recommendat=
ions</span></p></div></blockquote><div>In addition to the things=C2=A0alrea=
dy answered:</div><div><br></div><div>* What is the use case for logical=C2=
=A0replication? I assume your local replicas are able to keep up just fine.=
</div><div><br></div><div>* Check the nature of the work for problems, e.g.=
 ORM doing unnecessary/redundant updates, maintaining indexes that are not =
really needed</div><div><br></div><div>* Looks like your wal_segment_size w=
as boosted to 1GB. What drove that change?</div><div><br></div><div>* Yes, =
autovacuum could affect things - make sure log_autovacuum_min_durations is =
set</div><div><br></div><div>Cheers,</div><div>Greg</div><div><br></div><di=
v>=C2=A0</div></div></div>

--00000000000097166d0622f2a24e--