public inbox for pgsql-performance@postgresql.org
help / color / mirror / Atom feedFrom: Greg Sabino Mullane <htamfids@gmail.com>
To: masheed ullah <masheedullah@gmail.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Postgres DB backup is taking too much time
Date: Sun, 3 May 2026 20:20:05 -0400
Message-ID: <CAKAnmmLkUreQd3pkoiwZv1BFSc4WwAy5wQScUHuxKy7hxOhS_w@mail.gmail.com> (raw)
In-Reply-To: <CAHr8x_sQww+XNAFoHkyjYKJYq3CVcQLxJL0yaY3GHNzO3YV+bw@mail.gmail.com>
References: <CAHr8x_sQww+XNAFoHkyjYKJYq3CVcQLxJL0yaY3GHNzO3YV+bw@mail.gmail.com>
(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
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: pgsql-performance@postgresql.org
Cc: htamfids@gmail.com, masheedullah@gmail.com, pgsql-performance@lists.postgresql.org
Subject: Re: Postgres DB backup is taking too much time
In-Reply-To: <CAKAnmmLkUreQd3pkoiwZv1BFSc4WwAy5wQScUHuxKy7hxOhS_w@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