Hi, While de-spooling attributes into my postgres database for a full backup takes about two hours, I noticed that postgres was able to dump the entire database and create a brand new one including indexes in just a couple of minutes. It seems to me there's some room for improving bacula's de-spooling speed.
Since copying a database involves the use of the COPY command, I was wondering what it did differently (ie locking the entire table, transactions, etc.) to allow this speed. Could we use the copy command when we de-spool the attributes? Could we do the same thing the copy command it doing for speed? Cutting my postgres update time to minutes from hours would certainly make my backups run far smoother. -- Karl Hakimian [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
