Re: Export operation efficiency in read replica

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Export operation efficiency in read replica
Date: 2025-03-20 14:17:46
Message-ID: CANzqJaCyOFiYFnS+89_Par4e=Giqdvy4SDoxJ9Uju1ooXQqD9Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Mar 20, 2025 at 7:52 AM Siraj G <tosiraj(dot)g(at)gmail(dot)com> 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!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2025-03-20 14:20:08 Re: Postgres incremental database updates thru CI/CD
Previous Message Adrian Klaver 2025-03-20 14:04:55 Re: Export operation efficiency in read replica