public inbox for [email protected]
help / color / mirror / Atom feedFrom: Ron Johnson <[email protected]>
To: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: pg_dump and not MVCC-safe commands
Date: Mon, 20 May 2024 16:10:37 -0400
Message-ID: <CANzqJaBK-2fTYR06rtE3-3fkOcJQYJ0vgAwZD+nFO-95UbjxCg@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAKygsHQHhd4rzYcNCd8OJMH46saT1E+9+5MT2CgOCGgf_yaQAw@mail.gmail.com>
<CAECtzeUQ3hJYPM6k6_XqZLq=DygHbQ3+5YQLrv-ngcht2rQjQg@mail.gmail.com>
<CAKygsHRBRUhjGAQtqnbYPaXxJPvN2J49yS4ceee62iVG_jcuQQ@mail.gmail.com>
<[email protected]>
<CAKygsHS2rKkzRFh-SygCjR-TGLhpbWxci4Ms5BxoJ9KJ5DXhxA@mail.gmail.com>
<[email protected]>
On Mon, May 20, 2024 at 11:54 AM Christophe Pettus <[email protected]> wrote:
>
>
> > On May 20, 2024, at 08:49, PetSerAl <[email protected]> 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.
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: [email protected]
Cc: [email protected], [email protected]
Subject: Re: pg_dump and not MVCC-safe commands
In-Reply-To: <CANzqJaBK-2fTYR06rtE3-3fkOcJQYJ0vgAwZD+nFO-95UbjxCg@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