2008/9/9 Bill Moran <[EMAIL PROTECTED]>: > In response to Bob Hetzel <[EMAIL PROTECTED]>: > > After spending about 5 minutes looking at the code, I can tell you that > (from an SQL standpoint) dbcheck is enormously inefficient, and will > not get much better without a huge rewrite.
I would not say so. > Additionally, doing that > rewrite so that it results in improvements to all SQL platforms is > probably going to require that the code be broken into SQL-dependent > and SQL-independent sections. When working with dbcheck no problems (except for already described for MySQL). > > For example, the process to delete orphaned path records, first does > a select to get a list of IDs, then goes through a loop to delete each > record individually. If you wanted to speed this up in PostgreSQL, > you could do the following: > 1) Wrap all the DELETE statements in a transaction Removing records (in MySQL) goes very quickly. Yesterday I removed 750 K orphaned records ;) -- with best regards ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
