Red Hat Bugzilla – Bug 858643
[backup] using pg_dump --column-inserts slows down the restore process
Last modified: 2014-06-10 22:19:01 EDT
+++ This bug was initially created as a clone of Bug #858640 +++ Description of problem: Using the "--column-inserts" argument for pg_dump, increases the DB restore tens of times compared to not using it. Suggestion is to remove that param by default. Version-Release number of selected component (if applicable): rhev 3.0, rhev 3.1 How reproducible: Always Steps to Reproduce: 1. Generate a backup of rhevm and rhevm-history DB using pg_dump --column-inserts (check additional info) 2. Restore the backup Actual results: For big enough databases (10+ Gbs) I've seen the process can take from 30minutes to 2 hours Expected results: DB restore finishes in a few minutes, usually in less than a minute. Additional info: https://access.redhat.com/knowledge/docs/en-US/Red_Hat_Enterprise_Virtualization/3.0/html/Administration_Guide/Administration_Guide-Backing_Up.html#Administration_Guide-BU_Database_BU And RHEV 3.1 beta backup.sh script
this may also be relevant/affecting the installer which backsup the db
http://gerrit.ovirt.org/#/c/8134/
fixed in commit : 3a1c398
FailedQA - si20 - only backupdb.sh script contains the new option - the default for rhevm-upgrade is still '--column-inserts'. rhevm-setup-3.1.0-20.el6ev.noarch
Patch posted for review: http://gerrit.ovirt.org/#/c/8566/
as for now --column-inserts was removed from setup scripts, and open a bz866964 to track the move of usage in backup.sh- bz#866964 - rhevm-upgrade and rhevm-cleanup should use backup.sh to backup DB
ok - si21.1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-1506.html