From: Efrain J. Berdecia <ejberdecia@yahoo.com>
To: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Subject: pg_restore enhancements
Date: Wed, 22 Nov 2023 13:25:40 +0000 (UTC)
Message-ID: <362032628.6955904.1700659540303@mail.yahoo.com> (raw)
References: <362032628.6955904.1700659540303.ref@mail.yahoo.com>
After working for a site where we are constantly doing logical pg_dump to refresh environments I've come to miss features available in other RDBMS' refresh/restore utilities.
Someone could point me in the right direction otherwise, but pg_restore seems to be lacking the ability to resume a restore upon failure, is all or nothing with this guy. There also doesn't seem to be a way to control batch size when doing the COPY phase, therefore preventing the WAL directory from filling up and crashing the system.
IMHO, it would be nice to have a feature that would allow pg_restore to resume based on which part of the restore and/or object have already been restored.
When it comes to the COPY phase of the restore, it would be nice to be able to control batch size and resume COPY of a particular object upon failure.
Thanks in advance for any suggestions or the green light to post this to the PG-developer group :-)
Thanks,Efrain J. Berdecia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: ejberdecia@yahoo.com
Subject: Re: pg_restore enhancements
In-Reply-To: <362032628.6955904.1700659540303@mail.yahoo.com>
References: <362032628.6955904.1700659540303.ref@mail.yahoo.com> <362032628.6955904.1700659540303@mail.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox