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 1sh8i7-00DRVV-Ez for pgsql-general@arkaria.postgresql.org; Thu, 22 Aug 2024 14:22:47 +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 1sh8i5-002vOE-KZ for pgsql-general@arkaria.postgresql.org; Thu, 22 Aug 2024 14:22:46 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sh8i5-002vO6-8V for pgsql-general@lists.postgresql.org; Thu, 22 Aug 2024 14:22:45 +0000 Received: from mail-lf1-x12b.google.com ([2a00:1450:4864:20::12b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sh8i3-000uX6-Jl for pgsql-general@lists.postgresql.org; Thu, 22 Aug 2024 14:22:44 +0000 Received: by mail-lf1-x12b.google.com with SMTP id 2adb3069b0e04-5320d8155b4so1018902e87.3 for ; Thu, 22 Aug 2024 07:22:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724336562; x=1724941362; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pbaxP8YsebJcGPR+uAsWSha5d1EnyVYf/xdmJVBBNFI=; b=lEefPgBqU6k9SEc6LiS6nmkwhJAX81DWfczvu41ovOkReiCDzCPFKc6YsPwPzzFdsC 5BgbTSImz/syitEtgYaO48GqRYuWZdiit0rAdtmIUgV1olhz0EZjk7ForRRyqoDYcv0U jqq/YLIyNLYEE3OAcQFYkKAhGEfcR4ASHcL95/gkU9T1WcOgGL6jDV7guPonwSiY0zPf 3foJ7lf3JphG9ePhwRWdulqc7UaOTC3V/cPCoFQhyAPvm8Ew/9xBZrihwDlciZrjtphL Qv7GXVzClRMYwSrslEBpToOq3JHbi5bRlD5GnawasEH8hV2+Il5TS9fvdoroj+ExByS2 +MwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724336562; x=1724941362; h=cc: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=pbaxP8YsebJcGPR+uAsWSha5d1EnyVYf/xdmJVBBNFI=; b=fBtaD7c+4i7M6kDoE5DrfgFBC+GzY7QJs+/hqMhYM0/b7f4uRT4Gk1eTTKZ+xk604t OFYjzmpkpmq7Sal2NyGO8Kg4Fvy9taec74ODMc0/zP6naiokbzH5KRORxxVBblD24Enq cdCIm7xIVos8NY0NKIxzc4I+5KQQlDuZkNEbAEMLiQ8KL0aVKdZbD1RqA0VfnMdkwyJy qudPHoSgyRrcbmhl/ifMF/lFUdjwP+5DRZyEccPKqtGgOnGW5igCkpCo6sjeWRnBUsr9 lD7p38CIMoDVUDEuwTxo9Kh9vhV1crdAX+d7rtPuv5rtExJIjUZoynmI5QfSTTbM3JPp QIBA== X-Gm-Message-State: AOJu0Yxg9MubmcKnhWwuQWXVFLO5be4oiWxJL4i4TyxMjbw9OzK5qcpz 9FU8+FpZ91OhW9CaccIIsmF/rTSMicJrM6VViLplQEOskTGO0/Z5rtrFvC7SnlE7EekfJSV6GDo VdnYm/fOVEYlOs+BOd0Fjo1Og+o8= X-Google-Smtp-Source: AGHT+IHubtrhYQl8dB3FQT8qIEYPHtupmo4AHw6T5bmfwnk0BBi0cB5QWfWAt60My/PMPSe23H1sRhZHgj7SYsR9ZJ8= X-Received: by 2002:a05:6512:23aa:b0:533:4477:28a2 with SMTP id 2adb3069b0e04-5334fbfe88amr1375344e87.16.1724336561404; Thu, 22 Aug 2024 07:22:41 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Greg Sabino Mullane Date: Thu, 22 Aug 2024 10:22:02 -0400 Message-ID: Subject: Re: How to validate restore of backup? To: o1bigtenor Cc: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000003749160620466430" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000003749160620466430 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Aug 22, 2024 at 8:49=E2=80=AFAM o1bigtenor w= rote: > > > On Thu, Aug 22, 2024 at 6:24=E2=80=AFAM Ron Johnson > wrote: > >> That's great on small databases. Not so practical when they're big. >> >> So - - - - what is the recommended procedure for 'large' databases? > Use a real backup system like pgBackRest. Stop using pg_dump. Cheers, Greg --0000000000003749160620466430 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Aug 22, 2024 at 8:49=E2=80=AFAM o= 1bigtenor <o1bigtenor@gmail.com<= /a>> wrote:


<= div class=3D"gmail_quote">
On Thu, Aug= 22, 2024 at 6:24=E2=80=AFAM Ron Johnson <ronljohnsonjr@gmail.com> wrote:
That's great on small databases.=C2=A0 Not so practical when they'= re big.

So - - - - what is the recommended= procedure for 'large' databases?

Use a real backup system like pgBackRest. Stop using pg_du= mp.

Cheers,
Greg
--0000000000003749160620466430--