public inbox for [email protected]  

help / color / mirror / Atom feed

From: Mukesh Tanuku <[email protected]>
To: Laurenz Albe <[email protected]>
Cc: [email protected]
Subject: Re: Replication lag in Postgres
Date: Sat, 13 Jul 2024 11:32:53 +0530
Message-ID: <CAJzgB-E49Jm7eUfgLD+DxoxU5Zk5d6ZeTciPRC7jCem41txDEA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAJzgB-FgxbU15L3iyu84B8ZJdOvqfY9HM4s2Qc27f74=a43MKA@mail.gmail.com>
	<[email protected]>

Thank you for the information Laurenz Albe

On Fri, Jul 12, 2024 at 9:13 PM Laurenz Albe <[email protected]>
wrote:

> On Fri, 2024-07-12 at 20:41 +0530, Mukesh Tanuku wrote:
> > 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 of 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?
>
> When there is a delay, it is usually because replay at the standby is
> delayed.
> The WAL information is still replicated.  You won't lose that information
> on
> failover; it will just make the failover take longer.
>
> Unless you have a network problem, you should never lose more than a
> fraction
> of a second.
>
> Yours,
> Laurenz Albe
>

view thread (4+ messages)  latest in thread

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 using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: Replication lag in Postgres
  In-Reply-To: <CAJzgB-E49Jm7eUfgLD+DxoxU5Zk5d6ZeTciPRC7jCem41txDEA@mail.gmail.com>

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

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