public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-general <[email protected]>
Subject: Re: Export operation efficiency in read replica
Date: Thu, 20 Mar 2025 10:17:46 -0400
Message-ID: <CANzqJaCyOFiYFnS+89_Par4e=Giqdvy4SDoxJ9Uju1ooXQqD9Q@mail.gmail.com> (raw)
In-Reply-To: <CAC5iy60ZzcsxL1GKAdUdiqA7TFv_yQW3ZkN07VJM8J1Xkdk8Gg@mail.gmail.com>
References: <CAC5iy60ZzcsxL1GKAdUdiqA7TFv_yQW3ZkN07VJM8J1Xkdk8Gg@mail.gmail.com>
On Thu, Mar 20, 2025 at 7:52 AM Siraj G <[email protected]> wrote:
> Hello Experts!
>
> I have a DB with 1TB in size serving needs of one of our critical
> applications. I have a requirement to take export of the DB on a daily
> basis, but want to carry out this operation in read replica. The postgresql
> version is: 16.6
>
Use PgBackRest from the streaming replica.
> What would be the RPO of such backup?
>
Are you asking how long it takes to restore the backup back to the primary?
> What would be the impact on the READ REPLICA with a long running export
> operation?
>
Why not use the standby server (aka "read replica") as the hot standby in
case the Primary crashes hard?
Then pg_basebackup (or PgBackRest) to get the database back to the primary
once it's back up.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
view thread (3+ 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]
Subject: Re: Export operation efficiency in read replica
In-Reply-To: <CANzqJaCyOFiYFnS+89_Par4e=Giqdvy4SDoxJ9Uju1ooXQqD9Q@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