>>>>> On Fri, 3 Feb 2006 20:22:34 +0100, "Magnus Hagander" <[EMAIL PROTECTED]> >>>>> said: > > > > I'll try tuning things if you can get the data to me, or give me > > > access to the database. It's not always indexes. > > Sometimes it's more > > > along the lines of queries or vacuum. > > > > While setting up access to my data, I copied my bacula > > database to a new database and had quite an unexpected > > result. The query runs fast enough under the new database > > while still running slowly on the old one. > > This sounds like either table or index bloat. Typical reasons for tihs > are not doing vacuum (which obviously isn't your problem), or having too > few FSM pages. This can also be caused by not running vacuum earlier, > but doing it now - if you got far enough away from the good path you'll > need a VACUUM FULL to recover.
I get crazy index bloat with PostgreSQL 7.3.4 but running VACUUM FULL ANALYZE once a week keeps it mostly under control. At least I'm assuming it is index bloat, because running VACUUM ANALYZE once a week didn't fix it but droping and recreating the indexes does. __Martin ------------------------------------------------------- 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
