MIME-Version: 1.0
References: <CAKS+vVZSg=LDpFThxZQyemYE470Hbb15W-YZDHv=-fEZjML2QA@mail.gmail.com>
In-Reply-To: <CAKS+vVZSg=LDpFThxZQyemYE470Hbb15W-YZDHv=-fEZjML2QA@mail.gmail.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Thu, 22 Aug 2024 07:21:52 -0400
Message-ID: <CANzqJaAaQLUzmLKTaSUzrQc7Q+Ref3LO6nxs1=bZHOJFfSpDrw@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="000000000000459c17062043dede"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaAaQLUzmLKTaSUzrQc7Q%2BRef3LO6nxs1%3DbZHOJFfSpDrw%40mail.gmail.com>
Precedence: bulk

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

On Thu, Aug 22, 2024 at 7:06=E2=80=AFAM Vince McMahon <sippingonesandzeros@=
gmail.com>
wrote:

> Hi,
>
> I have some questions When doing pg_restore of backup of a database to a
> NEW server.
>
> Is there a way to ensure the data integrity is in tact, and user ID and
> access works liked how it was in the old server?
>

pg_restore is just a bunch of CREATE, COPY and ALTER statements, since
pg_restore replays what was generated by pg_dump.

There can be errors, of course.  That's why I  run "createdb $DB 2>
/dev/null" to ensure that there's something for pg_restore to drop, then
"pg_restore --create --clean --exit-on-error", and  *most importantly*,
check the return code!!!

How to properly handle the materialized views when backing up and restoring=
?
>
> Thanks.
>


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

--000000000000459c17062043dede
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 7:06=E2=80=AFAM V=
ince McMahon &lt;<a href=3D"mailto:sippingonesandzeros@gmail.com">sippingon=
esandzeros@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">Hi,<div di=
r=3D"auto"><br></div><div dir=3D"auto">I have some questions When doing pg_=
restore of backup of a database to a NEW server.=C2=A0=C2=A0</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">Is there a way to ensure the data int=
egrity is in tact, and user ID and access works liked how it was in the old=
 server?</div></div></blockquote><div><br></div><div>pg_restore is just a b=
unch of CREATE, COPY and ALTER statements, since pg_restore replays what wa=
s generated by pg_dump.=C2=A0</div><div>=C2=A0</div><div>There can be error=
s, of course.=C2=A0 That&#39;s why I=C2=A0=C2=A0run &quot;createdb $DB 2&gt=
; /dev/null&quot; to ensure that there&#39;s something for pg_restore to dr=
op, then &quot;pg_restore --create --clean=C2=A0--exit-on-error&quot;, and=
=C2=A0=C2=A0<b>most importantly</b>, check the return code!!!</div><div><br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"auto">=
<div dir=3D"auto"><div dir=3D"auto">How to properly handle the materialized=
 views when backing up and restoring?<br></div><div dir=3D"auto"><br></div>=
<div dir=3D"auto">Thanks.</div></div></div>
</blockquote></div><br clear=3D"all"><div><br></div><span class=3D"gmail_si=
gnature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><d=
iv dir=3D"ltr">Death to America, and butter sauce.<div>Iraq lobster!</div><=
/div></div></div>

--000000000000459c17062043dede--