> > If it did make a difference, you probably want to check the > values for > > your freespace map size. If there's not enough space in the > freespace > > map, vacuum won't be able to properly deal with the indexes so this > > can happen. > > Well ... feel free to correct me if I'm wrong, but vacuum > isn't capable of completely optimizing indexes. It only > deletes empty index pages. > The result is that over time, you accumulate lots of > half-empty index pages.
That depends entirely on your access pattern. But yes, in some access patterns that can happen. > REINDEX recompacts the indexes into full pages. This results > in less IO required to read the index off disk. Yes, but also the possibility of more IO required to write to the index since pagesplits may be needed in places not previously needed. (Looks like we may have fillfactor support in 8.2 for better control of these patterns) > Theoretically, you shouldn't have to REINDEX because the free > space will be reused in time, but it can get pretty > fragmented under normal usage. > Depending on the page size, this may or may not have a > noticeable impact on performance. It definitely has a > noticeable impact on disk usage. Yeah, it can have - again depending on the pattern. I haven't seen too much of it in my Bacula install, but it's certainly possible. //Magnus ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
