Feedback-ID: i76984098:Fastmail
Message-ID: <cd28b9d6-60ba-4d16-a1a2-8985e6a00a11@aklaver.com>
Date: Thu, 22 Aug 2024 08:36:32 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: How to validate restore of backup?
To: Vince McMahon <sippingonesandzeros@gmail.com>,
 "pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>
References: <CAKS+vVZSg=LDpFThxZQyemYE470Hbb15W-YZDHv=-fEZjML2QA@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAKS+vVZSg=LDpFThxZQyemYE470Hbb15W-YZDHv=-fEZjML2QA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/cd28b9d6-60ba-4d16-a1a2-8985e6a00a11%40aklaver.com>
Precedence: bulk

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
adrian.klaver@aklaver.com