public inbox for [email protected]
help / color / mirror / Atom feedFrom: Siraj G <[email protected]>
To: Guillaume Lelarge <[email protected]>
Cc: [email protected]
Subject: Re: Export operation efficiency in read replica
Date: Fri, 21 Mar 2025 19:37:46 +0530
Message-ID: <CAC5iy63orsh6axhJEtQGOs4qTHbnqTFrsj12SZx8MRgaJovyWw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAC5iy60ZzcsxL1GKAdUdiqA7TFv_yQW3ZkN07VJM8J1Xkdk8Gg@mail.gmail.com>
<[email protected]>
<CAC5iy60NgOv2nRYNwSh2n-Pj82eUjghgWjV2VCuQUABsAZ9uiw@mail.gmail.com>
<[email protected]>
<[email protected]>
Thank you everyone!
On Fri, Mar 21, 2025 at 7:23 PM Guillaume Lelarge <
[email protected]> wrote:
> On 20/03/2025 15:04, Adrian Klaver wrote:
> > On 3/20/25 05:58, Siraj G wrote:
> >> Hello Laurenz
> >>
> >> As per my understanding coming to a proper conclusion wrt RPO
> >
> > You still have not defined what RPO is.
> >
>
> I guess the OP is talking about Recovery Point Objective, which is one
> of two important parameters WRT to disaster recovery. It's the maximum
> data loss you agree on with your backup solution. That mostly depends on
> the database context, something we can't tell. And according to how much
> you agree to lose (one minute of activity? one hour?), you then can
> choose between pg_dump or PITR backups.
>
> But with a 1TB-database, I wouldn't dare using pg_dump. PITR backup is
> the only option.
>
>
> --
> Guillaume Lelarge
> Consultant
> https://dalibo.com
>
>
>
view thread (5+ messages)
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: Export operation efficiency in read replica
In-Reply-To: <CAC5iy63orsh6axhJEtQGOs4qTHbnqTFrsj12SZx8MRgaJovyWw@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