From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Verify data after backup and restore |
Date: | 2023-12-14 04:54:42 |
Message-ID: | CANzqJaAyHSKw0G0Xe1Q2vGr3pgFojNR=XhFrp2x0u_uj=r-saQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
If you think that "grep -E 'ERROR:|WARN:' pg_dump_$DB.log" is
insufficient, then write a script to get MIN(), MAX() and COUNT(*) of each
table before you do a pg_dump. After pg_restore, run the same script, but
pointed at the new database.
SELE the "first" (presumably ordered by primary key) and "last" records
On Wed, Dec 13, 2023 at 1:49 PM Rajesh Kumar <rajeshkumar(dot)dba09(at)gmail(dot)com>
wrote:
> Backup and restore I mean during downtime only. I wanted to double check
> what all things we need to validate after a successful restore. Like table
> count , all 14 objects count, first and last row of important tables, row
> count of each table like dat?
>
> On Wed, 13 Dec, 2023, 8:48 PM Ron Johnson, <ronljohnsonjr(at)gmail(dot)com>
> wrote:
>
>> On Wed, Dec 13, 2023 at 10:16 AM Pepe TD Vo <pepevo(at)yahoo(dot)com> wrote:
>>
>>> checking the backup files for size, date, and format; utilizing
>>> checksums or hashes to compare the backup files with the original data files
>>>
>>
>> How does that work on constantly changing tables?
>>
>>
From | Date | Subject | |
---|---|---|---|
Next Message | Rajesh Kumar | 2023-12-14 05:07:58 | Re: Verify data after backup and restore |
Previous Message | SOzcn | 2023-12-13 18:52:02 | Re: Reindex concurrently |