Re: pg_dump and not MVCC-safe commands

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: PetSerAl <petseral(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: pg_dump and not MVCC-safe commands
Date: 2024-05-20 15:53:58
Message-ID: DD46659C-6F79-465A-BD94-C69AEA49622C@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> 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.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2024-05-20 20:10:37 Re: pg_dump and not MVCC-safe commands
Previous Message PetSerAl 2024-05-20 15:49:46 Re: pg_dump and not MVCC-safe commands