Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1s95LH-00HDls-OP
	for pgsql-general@arkaria.postgresql.org; Mon, 20 May 2024 15:54:29 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-general-owner+archive@lists.postgresql.org>)
	id 1s95LH-0038Fb-Os
	for pgsql-general@arkaria.postgresql.org; Mon, 20 May 2024 15:54:27 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <xof@thebuild.com>)
	id 1s95LH-0038FT-Dr
	for pgsql-general@lists.postgresql.org; Mon, 20 May 2024 15:54:27 +0000
Received: from smtp91.iad3b.emailsrvr.com ([146.20.161.91])
	by magus.postgresql.org with esmtps  (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <xof@thebuild.com>)
	id 1s95LE-001DRT-6G
	for pgsql-general@lists.postgresql.org; Mon, 20 May 2024 15:54:26 +0000
X-Auth-ID: xof@thebuild.com
Received: by smtp12.relay.iad3b.emailsrvr.com (Authenticated sender: xof-AT-thebuild.com) with ESMTPSA id 3124DC0153;
	Mon, 20 May 2024 11:54:23 -0400 (EDT)
Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\))
Subject: Re: pg_dump and not MVCC-safe commands
From: Christophe Pettus <xof@thebuild.com>
In-Reply-To: <CAKygsHS2rKkzRFh-SygCjR-TGLhpbWxci4Ms5BxoJ9KJ5DXhxA@mail.gmail.com>
Date: Mon, 20 May 2024 08:53:58 -0700
Cc: Tom Lane <tgl@sss.pgh.pa.us>,
 Guillaume Lelarge <guillaume@lelarge.info>,
 pgsql-general@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DD46659C-6F79-465A-BD94-C69AEA49622C@thebuild.com>
References: <CAKygsHQHhd4rzYcNCd8OJMH46saT1E+9+5MT2CgOCGgf_yaQAw@mail.gmail.com>
 <CAECtzeUQ3hJYPM6k6_XqZLq=DygHbQ3+5YQLrv-ngcht2rQjQg@mail.gmail.com>
 <CAKygsHRBRUhjGAQtqnbYPaXxJPvN2J49yS4ceee62iVG_jcuQQ@mail.gmail.com>
 <3508051.1716215042@sss.pgh.pa.us>
 <CAKygsHS2rKkzRFh-SygCjR-TGLhpbWxci4Ms5BxoJ9KJ5DXhxA@mail.gmail.com>
To: PetSerAl <petseral@gmail.com>
X-Mailer: Apple Mail (2.3774.600.62)
X-Classification-ID: 729a0abe-7d20-4305-b202-ca37f4c0b6b9-1-1
List-Id: <pgsql-general.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-general@lists.postgresql.org>
List-Owner: <mailto:pgsql-general-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-general>
Archived-At: <https://www.postgresql.org/message-id/DD46659C-6F79-465A-BD94-C69AEA49622C%40thebuild.com>
Precedence: bulk



> On May 20, 2024, at 08:49, PetSerAl <petseral@gmail.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.=