| From: | o1bigtenor <o1bigtenor(at)gmail(dot)com> |
|---|---|
| To: | |
| Cc: | "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 13:58:32 |
| Message-ID: | CAPpdf5-_+dL1f9W2BaveRQhw0rX+eFfXBD4MfDJTQ6Yoe55sCQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
Can you try again?
(You forgot the first question - - - maybe you could try that one too - - -
what is the recommended procedure
for 'large' databases?)
Regards
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2024-08-22 14:22:02 | Re: How to validate restore of backup? |
| Previous Message | Ron Johnson | 2024-08-22 13:03:00 | Re: How to validate restore of backup? |