From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: How to validate restore of backup? |
Date: | 2024-08-22 11:23:38 |
Message-ID: | CANzqJaCxs4VwDZLw+JMdjjzvY8nC7MNvyH62GXNi2XTHAj3ghA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
That's great on small databases. Not so practical when they're big.
On Thu, Aug 22, 2024 at 7:10 AM Muhammad Usman Khan <usman(dot)k(at)bitnine(dot)net>
wrote:
> Hi Vince,
> For validation of databases, you can use the following approach
>
> /usr/pgsql-16/bin/pg_dump -d postgres -h localhost -p 5428 | md5sum >
> /var/lib/pgsql/db1.txt
> /usr/pgsql-16/bin/pg_dump -d postgres -h localhost -p 5420 | md5sum >
> /var/lib/pgsql/db2.txt
> diff db1.txt db2.txt
>
> By executing above queries, if diff is null then it means there is no
> difference between source and destination databases. Adjust your port and
> databases accordingly.
>
> On Thu, 22 Aug 2024 at 16:06, Vince McMahon <sippingonesandzeros(at)gmail(dot)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?
>>
>> How to properly handle the materialized views when backing up and
>> restoring?
>>
>> Thanks.
>>
>
--
Death to America, and butter sauce.
Iraq lobster!
From | Date | Subject | |
---|---|---|---|
Next Message | o1bigtenor | 2024-08-22 12:49:03 | Re: How to validate restore of backup? |
Previous Message | Ron Johnson | 2024-08-22 11:21:52 | Re: How to validate restore of backup? |