>>>>> "AH" == Alban Hertroys <dal...@solfertje.student.utwente.nl> writes:
AH> I don't think the reindex is necessary at all. That's a corner-case AH> operation that you shouldn't need in normal database operation. I AH> don't see why dspam would need it, at best there'd be some AH> high-volume scenarios where this turns out to be a gain, but for AH> those cases you need custom solutions anyway. High-volume is dependent on the size of the box. At least up through pg8 index entries are not re-used. They accumulate, increasing the size of the index files to the point that they can become too large for the shared_buffers. When that occurs, performace dies. For any temporal data set -- and dspam certainly qualifies -- regular use of reindex is the recomendation one gets from the pg lists. They will say that vacuum full is needed in only the most extremely temporal cases, but that regular reindexing is vital. How often, though, should vary based on the size of the tables, the size of the purge and the size of the box. And it probably should do vacuum, reindex, analyze rather than the current vacuum, analyze, reindex. -JimC -- James Cloos <cl...@jhcloos.com> OpenPGP: 1024D/ED7DAEA6 ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
