On 3/24/25 09:15, Dimitrios Apostolou wrote:
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.
It is doubtful that pg_dump/pg_restore will meet the requirements. You
are probably looking at some process that does incremental updates and
then restores from that. Something like pgbackrest:
https://pgbackrest.org/
comes to mind.
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
--
Adrian Klaver
adrian.kla...@aklaver.com
