| From: | Dimitrios Apostolou <jimis(at)gmx(dot)net> |
|---|---|
| To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Experience and feedback on pg_restore --data-only |
| Date: | 2025-03-24 16:15:01 |
| Message-ID: | d93ff45d-1d5b-71be-665a-883afb19ea8a@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Ron,
I read your reply in the mailing list archives as I'm not subscribed to
the list, and I'm copy-pasting a response here. Please include me as a
recipient in further replies.
> Why are you regularly having emergencies requiring the restoration of
> multi-TB tables to databases with lots of cruft?
>
> Fixing that would go a long way towards eliminating your problems with
> pg_restore.
I don't have emergencies yet. I'm testing the process of restoring the
database dump, and it takes more than 24 hours currently. A successful
test is vital to approve the process.
But the primary usage of pg_restore that I have is not to save me from
emergencies but to populate the dev database with recent data.
Regards,
Dimitris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2025-03-24 16:45:50 | Re: Today Page is not accessible - postgresql-15.spec |
| Previous Message | Adrian Klaver | 2025-03-24 16:09:19 | Re: Experience and feedback on pg_restore --data-only |