| From: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
|---|---|
| To: | masheed ullah <masheedullah(at)gmail(dot)com> |
| Cc: | pgsql-performance(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Postgres DB backup is taking too much time |
| Date: | 2026-05-04 00:20:05 |
| Message-ID: | CAKAnmmLkUreQd3pkoiwZv1BFSc4WwAy5wQScUHuxKy7hxOhS_w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
(This is more suitable for the pgsql-general list, you may get more/better
replies there)
There is nothing equivalent to ZDLRA in the Postgres world, but there are
certainly ways to reduce RTO. You are using replicas, and a tool that saves
WALs, so that really gets you 99% of the way there. Tools like pgBackrest
can do incremental backups, and parallel, delta-only restores, which can
wildly reduce both backup and restore times. RTO for Postgres can be
measured in seconds (e.g. Patroni handling a disk failure) to minutes (e.g.
someone dropped a table). Also see the recovery_min_apply_delay parameter.
If you give us a more specific use case / disaster scenario, we can give
more options and advice.
Cheers,
Greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ilya Anfimov | 2026-05-04 09:29:11 | Re: Postgres DB backup is taking too much time |
| Previous Message | manish yadav | 2026-05-03 17:16:36 | Re: Postgres DB backup is taking too much time |