-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 21.09.2011 14:58, schrieb Gavin McCullagh: > Then a couple of months ago I noticed a new detail in the wiki about > _removing_ bogus indexes. It turns out that by adding extra indexes you > can slow down MySQL SELECT queries (I think someone said it doesn't always > choose the optimal/correct index). > > http://wiki.bacula.org/doku.php?id=faq
The FAQ first (in #why_does_dbcheck_take_forever_to_run) advises to creade indexes on File.PathId and File.FilenameId and later on (in #restore_takes_a_long_time_to_retrieve_sql_results_from_mysql_catalog) to drop them if they exist. Since Bacula version 5, dbcheck(8) warns if these indexes do not exist and offers to create temporary indexes for them, although the latter FAQ entry appears to warn against allowing that, too. Perhaps someone could clarify a bit how to decide which indexes to create or drop when? Thanks, Tilman -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk6RkKcACgkQ780oymN0g8Ot/gCeLi/IwY1jbCB3h50SosAphq0p DGUAniaOwMa+nRpylSVmOnAE45XA5q21 =IB2p -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
