[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bacula-devel] small dbcheck patch for mysql

2008/9/10 Kern Sibbald <kern@xxxxxxxxxxx>:
>> BTW, dbcheck is slightly unsafe since it runs without transactions
>> today: a filename entry can be orphaned during the SELECT, but reused
>> by a backup job inserting data before the DELETE.  this means you
>> should not run dbcheck while backups are running (or at likely to
>> insert attributes).
> Yes, that is correct.  We probably should use some sort of table lock, but for
> the moment, you just need to be careful.

If dbcheck block table and will work long, it may inhibit Jobs.
If interrupt dbcheck (i.e. ctrl+c), it may happen that lock did not
will be unlock.

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
Bacula-devel mailing list

This mailing list archive is a service of Copilot Consulting.