| From: | Guillaume Lelarge <guillaume(dot)lelarge(at)dalibo(dot)com> |
|---|---|
| To: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Export operation efficiency in read replica |
| Date: | 2025-03-21 13:52:55 |
| Message-ID: | f2fbd780-f0c1-4aac-b136-913da043e82c@dalibo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Siraj G | 2025-03-21 14:07:46 | Re: Export operation efficiency in read replica |
| Previous Message | Michael Paquier | 2025-03-21 00:54:55 | Re: query_id: jumble names of temp tables for better pg_stat_statement UX |