Red Hat Bugzilla – Bug 858640
[backup] using pg_dump --column-inserts slows down the restore process
Last modified: 2016-02-10 14:16:02 EST
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
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
For big enough databases (10+ Gbs) I've seen the process can take from 30minutes to 2 hours
DB restore finishes in a few minutes, usually in less than a minute.
And RHEV 3.1 beta backup.sh script
We'll need to clone this for 3.1 if Alex agrees that this is the way to go.
Alex, can you comment on whether that parameter should be removed from the backup command?
Have you also raised this as a bug against the backup.sh script?
It makes more sense to me to start there than trying to get it removed from the documentation first.
So long as that parameter remains in the backup script we ship and support, I'll leave it in the documentation. If the person who is responsible for that script removes it from the script, I'll remove it from the documentation.
I'm going to change the component to this bug to ovirt-engine-backend. I've added myself to the cc list so I'll be watching what happens to this bug going forward.
If someone there decides to remove the "--column-inserts" argument for pg_dump in the backup.sh script, then we'll clone the bug back to documentation, and I'll proceed accordingly.
Yes, it's already in 3.1.:
Change was accepted, has all the flags and a patch was posted.