MIME-Version: 1.0
References: <CAKS+vVZSg=LDpFThxZQyemYE470Hbb15W-YZDHv=-fEZjML2QA@mail.gmail.com>
 <CAPnRvGsmb57R7cD3KFjN6p=YrxXen-E_Xbs9QKHx7REKQfz--g@mail.gmail.com>
 <CANzqJaCxs4VwDZLw+JMdjjzvY8nC7MNvyH62GXNi2XTHAj3ghA@mail.gmail.com> <CAPpdf5_mu_DJCbDY99Xa+BBJX0sMZo=yshohDT0TgUdjmMqRrg@mail.gmail.com>
In-Reply-To: <CAPpdf5_mu_DJCbDY99Xa+BBJX0sMZo=yshohDT0TgUdjmMqRrg@mail.gmail.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Thu, 22 Aug 2024 09:03:00 -0400
Message-ID: <CANzqJaCHA3jgDfYKVGM3uqf=MdkMQtKqbCnOH2OWqjntfYtLKQ@mail.gmail.com>
Subject: Re: How to validate restore of backup?
To: "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000e4418206204547be"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaCHA3jgDfYKVGM3uqf%3DMdkMQtKqbCnOH2OWqjntfYtLKQ%40mail.gmail.com>
Precedence: bulk

--000000000000e4418206204547be
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Aug 22, 2024 at 8:49=E2=80=AFAM o1bigtenor <o1bigtenor@gmail.com> w=
rote:

>
>
> On Thu, Aug 22, 2024 at 6:24=E2=80=AFAM Ron Johnson <ronljohnsonjr@gmail.=
com>
> 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.

--=20
Death to America, and butter sauce.
Iraq lobster!

--000000000000e4418206204547be
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Thu, Aug 22, 2024 at 8:49=E2=80=AFAM o=
1bigtenor &lt;<a href=3D"mailto:o1bigtenor@gmail.com">o1bigtenor@gmail.com<=
/a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><=
div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Aug=
 22, 2024 at 6:24=E2=80=AFAM Ron Johnson &lt;<a href=3D"mailto:ronljohnsonj=
r@gmail.com" target=3D"_blank">ronljohnsonjr@gmail.com</a>&gt; wrote:<br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div=
>That&#39;s great on small databases.=C2=A0 Not so practical when they&#39;=
re big.</div><br></div></blockquote><div>So - - - - what is the recommended=
 procedure for &#39;large&#39; databases?</div><div><br></div><div>(Might b=
e useful to have a definition for what a large database is as well.)=C2=A0<=
/div></div></div></blockquote><div><br></div><div>&quot;Large&quot; is when=
 it takes too long to run <b>TWO</b>=C2=A0text mode pg_dump commands <b>in =
addition to</b> the pg_dump and pg_restore.</div></div><div><br></div><span=
 class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"g=
mail_signature"><div dir=3D"ltr">Death to America, and butter sauce.<div>Ir=
aq lobster!</div></div></div></div>

--000000000000e4418206204547be--