MIME-Version: 1.0
References: <CAJzgB-FgxbU15L3iyu84B8ZJdOvqfY9HM4s2Qc27f74=a43MKA@mail.gmail.com>
In-Reply-To: <CAJzgB-FgxbU15L3iyu84B8ZJdOvqfY9HM4s2Qc27f74=a43MKA@mail.gmail.com>
From: Muhammad Imtiaz <imtiaz.m@bitnine.net>
Date: Sat, 13 Jul 2024 14:34:21 +0500
Message-ID: <CANwR1ORFW3-JaRE+o3riD2x=t-y0=NQK=7VFiC4EgCF8kJJ+TA@mail.gmail.com>
Subject: Re: Replication lag in Postgres
To: Mukesh Tanuku <mukesh.postgres@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000122bd2061d1db46f"
Archived-At: <https://www.postgresql.org/message-id/CANwR1ORFW3-JaRE%2Bo3riD2x%3Dt-y0%3DNQK%3D7VFiC4EgCF8kJJ%2BTA%40mail.gmail.com>
Precedence: bulk

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

Hi,

I recommend the following configurations/options in this case:

=E2=80=A2 wal_sender_timeout: This setting determines how long the primary =
server
waits for the standby server to acknowledge receipt of WAL data. Adjusting
this can help ensure timely data transfer.

=E2=80=A2 wal_keep_size: Ensures that enough WAL files are retained for the=
 standby
to catch up if it falls behind.

=E2=80=A2 checkpoint_timeout: Adjust the checkpoint frequency to ensure WAL=
 files
are regularly flushed and sent to the standby server regularly.

=E2=80=A2 pg_receivewal: Use this tool to continuously archive WAL files to=
 a safe
location.It will helpful if there is a delay in streaming replication, you
have a backup of WAL files.

Regards,
Muhammad Imtiaz

On Fri, 12 Jul 2024, 20:11 Mukesh Tanuku, <mukesh.postgres@gmail.com> wrote=
:

> Hello everyone.
> Firstly thanks to the community members who are addressing all the querie=
s
> that are posted. Those give us more insights about the issues/doubts in t=
he
> postgres.
>
> I have a question with postgres HA setup.
> We are setting up a 2 node postgres cluster with async streaming
> replication, we want to define a RPO (Recovery point objective) in case o=
f
> primary failure.
>
> How can we best define the RPO in this setup? since it's an async
> streaming replication setup there might be a chance of data loss which is
> proportional to the replication delay.
>
> Is there any way we can configure the delay duration, like for example to
> make sure every 10 mins the standby sync has to happen with primary?
>
> Thank you
> Regards
> Mukesh T
>
>

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

<div dir=3D"auto"><div dir=3D"auto">Hi,</div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">I  recommend the following configurations/options in this c=
ase:
<br><br>=E2=80=A2 wal_sender_timeout: This setting determines how long the =
primary server waits for the standby server to acknowledge receipt of WAL d=
ata. Adjusting this can help ensure timely data transfer.
<br><br>=E2=80=A2 wal_keep_size: Ensures that enough WAL files are retained=
 for the standby to catch up if it falls behind.
<br><br>=E2=80=A2 checkpoint_timeout: Adjust the checkpoint frequency to en=
sure WAL files are regularly flushed and sent to the standby server regular=
ly.
<br><br>=E2=80=A2 pg_receivewal: Use this tool to continuously archive WAL =
files to a safe location.It will helpful if there is a delay in streaming r=
eplication, you have a backup of WAL files.<br></div><div dir=3D"auto"><br>=
</div><div dir=3D"auto">Regards,</div><div dir=3D"auto">Muhammad Imtiaz</di=
v></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr=
">On Fri, 12 Jul 2024, 20:11 Mukesh Tanuku, &lt;<a href=3D"mailto:mukesh.po=
stgres@gmail.com">mukesh.postgres@gmail.com</a>&gt; wrote:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><div dir=3D"ltr">Hello everyone.=C2=A0<div>Firstly =
thanks to the community members=C2=A0who are addressing all the queries tha=
t are posted. Those give us more insights=C2=A0about the issues/doubts in t=
he postgres.=C2=A0</div><div><br><div>I have a question with postgres HA se=
tup.<br><div>We are setting up a 2 node postgres cluster with async streami=
ng replication, we want to define a RPO (Recovery point objective) in case =
of primary failure.=C2=A0</div><div><br></div><div>How can we best define=
=C2=A0the RPO in this setup? since it&#39;s an async streaming replication =
setup there might be a chance of data loss which is proportional to the rep=
lication delay.=C2=A0</div><div><br></div><div>Is there any way we can conf=
igure=C2=A0the delay duration, like for example to make sure every 10 mins =
the standby sync has to happen with primary?=C2=A0</div><div><br></div><div=
>Thank you</div><div>Regards=C2=A0</div><div>Mukesh T</div><div></div><div>=
<br></div></div></div></div>
</blockquote></div>

--000000000000122bd2061d1db46f--