From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: How to validate restore of backup? |
Date: | 2024-08-22 14:38:07 |
Message-ID: | CANzqJaCZw9B=dnFBuamtu5W3_43E5zyY3Qg2UZNrc2y_3_uMWA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, Aug 22, 2024 at 9:59 AM o1bigtenor <o1bigtenor(at)gmail(dot)com> wrote:
> On Thu, Aug 22, 2024 at 8:03 AM Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
> wrote:
>
>> On Thu, Aug 22, 2024 at 8:49 AM o1bigtenor <o1bigtenor(at)gmail(dot)com> wrote:
>>
>>> On Thu, Aug 22, 2024 at 6:24 AM Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
>>> wrote:
>>>
>>>> That's great on small databases. Not so practical when they're big.
>>>>
>>>> So - - - - what is the recommended procedure for 'large' databases?
>>>
>>> (Might be useful to have a definition for what a large database is as
>>> well.)
>>>
>>
>> "Large" is when it takes too long to run *TWO* text mode pg_dump
>> commands *in addition to* the pg_dump and pg_restore.
>>
>>
> Hmmmmmmmmm - - - - I'd say that's about as neat a non-answer as I've ever
> seen.
>
Eh? If you've got hundreds of hours of down time to pipe a text-mode
pg_dump of a TB-sized database through md5sum. twice, then that database
isn't too big. I don't have that much down time; thus, it's "too big".
Can you try again?
>
> (You forgot the first question - - - maybe you could try that one too - -
> - what is the recommended procedure
> for 'large' databases?)
>
I already did, in my message three hours ago.
--
Death to America, and butter sauce.
Iraq lobster!
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2024-08-22 15:36:32 | Re: How to validate restore of backup? |
Previous Message | Ron Johnson | 2024-08-22 14:32:33 | Re: How to validate restore of backup? |