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
