| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_dump and not MVCC-safe commands |
| Date: | 2024-05-20 20:10:37 |
| Message-ID: | CANzqJaBK-2fTYR06rtE3-3fkOcJQYJ0vgAwZD+nFO-95UbjxCg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, May 20, 2024 at 11:54 AM Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
>
> > On May 20, 2024, at 08:49, PetSerAl <petseral(at)gmail(dot)com> wrote:
> > Basically, you need application cooperation to make
> > consistent live database backup.
>
> If it is critical that you have a completely consistent backup as of a
> particular point in time, and you are not concerned about restoring to a
> different processor architecture, pg_basebackup is a superior solution to
> pg_dump.
>
Single-threaded, and thus dreadfully slow. I'll stick with PgBackRest.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2024-05-21 10:02:56 | Re: How to update upper-bound of tstzrange ? |
| Previous Message | Christophe Pettus | 2024-05-20 15:53:58 | Re: pg_dump and not MVCC-safe commands |