public inbox for [email protected]
help / color / mirror / Atom feedFrom: Adrian Klaver <[email protected]>
To: Vince McMahon <[email protected]>
To: pgsql-generallists.postgresql.org <[email protected]>
Subject: Re: How to validate restore of backup?
Date: Thu, 22 Aug 2024 08:36:32 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAKS+vVZSg=LDpFThxZQyemYE470Hbb15W-YZDHv=-fEZjML2QA@mail.gmail.com>
References: <CAKS+vVZSg=LDpFThxZQyemYE470Hbb15W-YZDHv=-fEZjML2QA@mail.gmail.com>
On 8/22/24 04:06, Vince McMahon wrote:
> Hi,
>
> I have some questions When doing pg_restore of backup of a database to a
> NEW server.
How large a backup?
>
> 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?
As to user access, write tests that cover that and run on the new cluster.
Data is trickier and if that is possible to a degree of certainty is
going to depend on answer to the first question above.
>
> How to properly handle the materialized views when backing up and restoring?
create materialized view prj_mv(p_item_no, year) as select p_item_no,
year from projection with data;
pg_dump -d production -U postgres -h localhost -t projection -t prj_mv
-f prj.sql
In prj.sql:
CREATE MATERIALIZED VIEW public.prj_mv AS
SELECT p_item_no,
year
FROM public.projection
WITH NO DATA;
COPY public.projection ( ...
[...]
REFRESH MATERIALIZED VIEW public.prj_mv;
It is done for you.
>
> Thanks.
--
Adrian Klaver
[email protected]
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: How to validate restore of backup?
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox