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 ) id 1s99LV-000756-UU for pgsql-general@arkaria.postgresql.org; Mon, 20 May 2024 20:10:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s99LU-004rAl-9L for pgsql-general@arkaria.postgresql.org; Mon, 20 May 2024 20:10:56 +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 ) id 1s99LT-004rAd-UY for pgsql-general@lists.postgresql.org; Mon, 20 May 2024 20:10:55 +0000 Received: from mail-ot1-x336.google.com ([2607:f8b0:4864:20::336]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1s99LN-001FIx-P0 for pgsql-general@lists.postgresql.org; Mon, 20 May 2024 20:10:55 +0000 Received: by mail-ot1-x336.google.com with SMTP id 46e09a7af769-6f0f252db4dso1581229a34.0 for ; Mon, 20 May 2024 13:10:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716235848; x=1716840648; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=i27ILedoIiQ9SlsjeST9E5ZLpcyB81nDDWxIjH+1G2E=; b=FrAefdWEBcHpf+vFaId10v+mr5ev/6/pgtwDKZfepOZUOIdmJ1vCLv4TtYnd5GIqbh qe1w640ojldMZOcE9KA3ZoG5oTJJKxi3XrCIEoWhQmCC/PXqb4L5yXx9gabMCNNd1wAq JzVUCOmlYlbkw4Sgodb4h31sPd0f8PGfBpqsQksKo1zXSw3z9rNsifTr/9sIrcDA2CMr xxhL8MSZRP65qzaGLZ07O+snGz95313o5v99q+OkO097HZ+EvkjcBj9G46s+Zm4F5UmR Imwn+8QUOgJWMgHjYOwZXNLHG8NvmLSctMV+6Cye8vJEWHIwFHvPeQMGStg94K2ceQYQ L1VQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716235848; x=1716840648; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=i27ILedoIiQ9SlsjeST9E5ZLpcyB81nDDWxIjH+1G2E=; b=KOL6fsGboqtSpcCc+3RXNpFU4Ke5QBfyFVkvuKWX/Ukuhh8rPQ10QPHkwLgQdWWrfw 9jFnj9uXv0VY7vIu3hp8q/rBl6PEPRdCFWHIPfNqRvYzyLHsEnkWoo38aAjLbvthSH5g WFacpP9Qrhejh2qE/ODZMmeqgPgSy0r4se9s4gqAVBFQxoRB2Ku+sbLbuPGoTfSCfQjv uQXNxf9mo4WMRJ5fbYg4TM2XJxLfO759pNn69bxZdQk+bvQoU5eHLbJ0KeNCeakCKsv8 WFOf2qfFAhYzEwY/HzhVMmWHClUlIf7WUI0J41vm/K9eJHrK0vsQS7aM7FN9koIuCPKz X+mA== X-Gm-Message-State: AOJu0Ywtol2MO+i2mykT1Ng61jxXiFnsC7BQ9MdX3AsajIXX70ViYUbg hl6fRVvaqXI7jpiQCKjfs//a0USDmk9iu0BhIUiv6P07VhetgfhE8CRXFNCYZMCYQcDjIuZGukt 13VMsyEs/RBjZCtPKd5nSynOghjmZxA== X-Google-Smtp-Source: AGHT+IF4loHJchLtlFf7rk46cRd8SPnXy86qiN+ROShkxpwM8yi7OTpCVZrisFx9GxciaoUykoQ+3DxLeOeJxwqmYBc= X-Received: by 2002:a05:6870:9a12:b0:23c:6619:ee3b with SMTP id 586e51a60fabf-24172a51e55mr37699328fac.13.1716235848302; Mon, 20 May 2024 13:10:48 -0700 (PDT) MIME-Version: 1.0 References: <3508051.1716215042@sss.pgh.pa.us> In-Reply-To: From: Ron Johnson Date: Mon, 20 May 2024 16:10:37 -0400 Message-ID: Subject: Re: pg_dump and not MVCC-safe commands To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000016c6ee0618e84cda" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000016c6ee0618e84cda Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Mon, May 20, 2024 at 11:54=E2=80=AFAM Christophe Pettus wrote: > > > > On May 20, 2024, at 08:49, PetSerAl 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. --00000000000016c6ee0618e84cda Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Mon, May 20, 2024 at 11:54=E2=80=AFAM = Christophe Pettus <xof@thebuild.com<= /a>> wrote:


> 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 part= icular point in time, and you are not concerned about restoring to a differ= ent processor architecture, pg_basebackup is a superior solution to pg_dump= .
=C2=A0
Single-threaded, and thus dreadfull= y slow.=C2=A0 I'll stick with PgBackRest.

--00000000000016c6ee0618e84cda--