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 1sh8LO-00DMhA-DZ for pgsql-general@arkaria.postgresql.org; Thu, 22 Aug 2024 13:59:18 +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 1sh8LL-002nMF-LZ for pgsql-general@arkaria.postgresql.org; Thu, 22 Aug 2024 13:59:16 +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 1sh8LL-002nM6-AW for pgsql-general@lists.postgresql.org; Thu, 22 Aug 2024 13:59:15 +0000 Received: from mail-lj1-x229.google.com ([2a00:1450:4864:20::229]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sh8LE-000xZ8-Qj for pgsql-general@lists.postgresql.org; Thu, 22 Aug 2024 13:59:15 +0000 Received: by mail-lj1-x229.google.com with SMTP id 38308e7fff4ca-2f401c20b56so8622661fa.0 for ; Thu, 22 Aug 2024 06:59:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724335149; x=1724939949; darn=lists.postgresql.org; h=cc:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=bdnNOeTLUT9v8IAUspksvTn+s5Wepq3HzI13HJJs61M=; b=gmJtalSG5j1JzjxshXdHFRos8Hw20arI/+K5db+k1liid9o8BiJwWWXcYpD1KpSHp/ IdFPBvgTAoAiQLLjveqHgTRsTnY0fmLZOQHePXrphdgnnCN3s+hI8N3jCX4B/oBGR/7/ /hDywHb1siXzJtRL4J/MenHGRqgsSrMqD18/59pna4UTImatEV9zsbJgpk0StCdKgf6B gru/tl4fQbYKx6zjnr6UOpBVUp4DNFY7RwiJKx2cNTUgt06e8dAK3cG6xl2XCON+edcI lxlNLmYls45aJb9V7eTqrzoBLIr5HMYRUaRKhK+sjAjAaP/ny/ve/8ybVfVaA20Bs6mA KnrA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724335149; x=1724939949; h=cc: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=bdnNOeTLUT9v8IAUspksvTn+s5Wepq3HzI13HJJs61M=; b=W4gmcxwlkACJO87LgVE3R4iIhRNYwunTJ5Lz1zqEQBO2A4REr2uEfIBlH0Bo8CwlJa xtS8xjor/Ol1hRfARm0hwYPvjeIp3LnDFyMwDUBZIVqT4HZF9Lck6dppGOdSRbtOT9s+ OZzo87RL+zDvbFunJDsbgsyuDaIQ+EskUackV5U3NUJX5IjnOpqQCRfiPiFcVejPan4X WNe9Nr162Cl7eeNFISbTSvaZfR8K38tLzpZAy3uGjU08iREvKkmTmE9lv6XfsTF/g5cc vf9T3+t7EpvQx8X4VyHw/egWrKmZmL6NJmbX/N5MkhU3q91vAOKAnRQYwtbKTovyMIq4 wGOQ== X-Gm-Message-State: AOJu0YyvV8IBqTvMlhtOjPHNL4AfpPPWeEjJoUlxh7RMsA228y7g6f1Z BBVvSzV/bPCSbrOvmjnlVMHtitAOKzqoLksxM0u9LH0Ygbrx3bwiIpZdDSRU1i0w105yYXBkvLk 4J48Ce8hVjxSMHcXC6kSMB4jgLGSOEhEw X-Google-Smtp-Source: AGHT+IHscyws4d7g/LdepmeWWgXBWJxXKWBMRbQeD6kRW4bwGTii6BxlnM3ZFRJmpZthY1ZWBwUHHHZPuPoeCFT3f4M= X-Received: by 2002:a05:6512:3b0f:b0:52e:fa08:f0f5 with SMTP id 2adb3069b0e04-5334ca7d583mr1220631e87.13.1724335148595; Thu, 22 Aug 2024 06:59:08 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: o1bigtenor Date: Thu, 22 Aug 2024 08:58:32 -0500 Message-ID: Subject: Re: How to validate restore of backup? Cc: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="00000000000001851c06204610e9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000001851c06204610e9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Aug 22, 2024 at 8:03=E2=80=AFAM Ron Johnson wrote: > On Thu, Aug 22, 2024 at 8:49=E2=80=AFAM o1bigtenor = wrote: > >> >> >> 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? >> >> (Might be useful to have a definition for what a large database is as >> well.) >> > > "Large" is when it takes too long to run *TWO* text mode pg_dump commands= *in > addition to* the pg_dump and pg_restore. > > Hmmmmmmmmm - - - - I'd say that's about as neat a non-answer as I've ever seen. Can you try again? (You forgot the first question - - - maybe you could try that one too - - - what is the recommended procedure for 'large' databases?) Regards --00000000000001851c06204610e9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Aug 22, 2024 at 8:03=E2=80=AF= AM Ron Johnson <ronljohnsonjr= @gmail.com> wrote:
On Thu, Aug 22, 2024 at 8:49= =E2=80=AFAM o1bigtenor <o1bigtenor@gmail.com> wrote:


On Thu, Aug 22, 2024 at 6:24=E2=80=AFAM Ron Johnson &= lt;ronljohnson= jr@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= ?

(Might be useful to have a definition for what a= large database is as well.)=C2=A0

<= /div>
"Large" is when it takes too long to run TWO=C2= =A0text mode pg_dump commands in addition to the pg_dump and pg_rest= ore.


Hmmmmmmmmm - - -= - I'd say that's about as neat a non-answer as I've ever seen.= =C2=A0

Can you try again?

(You forgot the first question - - - maybe you could try that one too - - = - what is the recommended procedure
for 'large' data= bases?)

Regards
--00000000000001851c06204610e9--