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 1sh5gP-00CmPt-6q for pgsql-general@arkaria.postgresql.org; Thu, 22 Aug 2024 11:08:49 +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 1sh5gN-001TJD-Ea for pgsql-general@arkaria.postgresql.org; Thu, 22 Aug 2024 11:08:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sh5du-001OZc-0r for pgsql-general@lists.postgresql.org; Thu, 22 Aug 2024 11:06:14 +0000 Received: from mail-yb1-xb2f.google.com ([2607:f8b0:4864:20::b2f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sh5ds-000t9m-7k for pgsql-general@lists.postgresql.org; Thu, 22 Aug 2024 11:06:13 +0000 Received: by mail-yb1-xb2f.google.com with SMTP id 3f1490d57ef6-e1205de17aaso699077276.2 for ; Thu, 22 Aug 2024 04:06:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1724324771; x=1724929571; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=BrwLPXX23W+WUPhWhN2ihQzectVbQqokiwQal0VHlyo=; b=ahMoEbKmgRPQLnWg/0lLmOtAGTAbX87HUDAmuS3Ca8eZybe2j91JSOiSVUUTsyhWDg BsVuw6zx7D4OMSJCEEQ/G4sA0ueO5jNKPwnBc9hDAdhaKWe8wyqp+bC7gETLDdjMsnoo HTlVcWRqS7N1Iy3wFIelrnGEJqSMSYjnHKBSCMA37XGO0xNeE1jeaM8WwjRLMq8JrJ+w 6fN4kDQi3ox2JGLutygrJvcneQSY0cdIktdO/MCrQijrTf+rtO5rAfx1vm9wGTyVDF3z HfiUzHIfc8NPgWCzQ8BH9OLMoNBHz7ii2EUQ5pCzhrhVQ5e3bHfGIyBTsCxMaqAscs4z Qa9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1724324771; x=1724929571; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=BrwLPXX23W+WUPhWhN2ihQzectVbQqokiwQal0VHlyo=; b=XVzicvjDnHAH3iv6jbFwbuCMpCZbYszu4qhp/pMFGOc4mH2PcPSYpd3nt3bavYjwBo NzldzCgTU1v5LFrHNJOr6+2TZqwsJDa3ngt04CBNqQbSE7lLrVw65mFgS3cA3kMDT8wa j2sXyljf2qFqKlYllgALWJ+m8x2IodgVEnzvneddH6BesWYBmSBjuAb6pR/28kmssdzZ 7d8KHtN8KAG570UvE8rNSrvidjVMt1cGguPLcqdPPJkLhahNX8CzAK9tZfcKreTVg/QJ NslPCeoX5PdCdJNNU3jPmHz6uguErYy/1T21N+b4ZSF/JZVSx3B4A0+CVk4wNrd33Cz7 4cNg== X-Gm-Message-State: AOJu0YzODLesDFx9d8YqbuPSaezh5Q/2aHc1hlZpFHQWLfraJIm//kAK CNcIQhqb95uWQ0iJ71fpExzr77eEQ5zhmVJNbojvdLaP7RGZ+LrT5onEMIkw+cQPmUdZT5MjJ22 JD9SN9/hHu97KFdH4xKZVZL1/l8D0og== X-Google-Smtp-Source: AGHT+IHeXobwihI8nqHR7S9aS1fqFrT4hIL9xqvWuITio/DVrqXmv5rFH+yCeqMlcReVXuzzOyG17D7yQoPr/9hE75E= X-Received: by 2002:a05:6902:2484:b0:e11:7f99:f75b with SMTP id 3f1490d57ef6-e166551dbd0mr5900799276.42.1724324771412; Thu, 22 Aug 2024 04:06:11 -0700 (PDT) MIME-Version: 1.0 From: Vince McMahon Date: Thu, 22 Aug 2024 07:06:00 -0400 Message-ID: Subject: How to validate restore of backup? To: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000007a47a6062043a5c9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007a47a6062043a5c9 Content-Type: text/plain; charset="UTF-8" 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? How to properly handle the materialized views when backing up and restoring? Thanks. --0000000000007a47a6062043a5c9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,

I have s= ome questions When doing pg_restore of backup of a database to a NEW server= .=C2=A0=C2=A0

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?

How to properly handle the materialized views when backing up and res= toring?

Thanks.
--0000000000007a47a6062043a5c9--