> Or do you get significantly different plans from EXPLAIN? Could be a > missing ANALYZE?
I tried running a Vacuum analyze on my database and then while trying things between the newly created database and my old one I lost track of which one I was in and started doing some of these queries that were so slow, the old database seems to be matching the speed of the newly created one. So at this point, I don't really know what seems to have speeded it up, but it does seem to be doing much better. > In general for a system like Bacula, I'd advise against using > pg_autovacuum. There's always the risk that it'll kick in in the middle > of a Bacula job. Since you almost certainly have a time when there are > no jobs being processed in the database (I use th etime right after the > catalog backup), you should just run a manual database-wide VACUUM > ANALYZE then. Good suggestion. I was wondering if that was a better way to deal with this particular database. -- 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
