Bug #14656 Allow user to customize DB_LOG_AUTOREMOVE flag for BDB
Submitted: 4 Nov 2005 19:46 Modified: 31 Aug 2006 14:43
Reporter: Jim Winstead Email Updates:
Status: Unsupported Impact on me:
None 
Category:MySQL Server: BDB Severity:S4 (Feature request)
Version:5.1 OS:Any (All)
Assigned to: CPU Architecture:Any

[4 Nov 2005 19:46] Jim Winstead
Description:
Currently, we always configure BDB to remove log files when it is done with them. This could be made subject to user control.

How to repeat:
Use BDB, watch log files get deleted after they are no longer in use.

Suggested fix:
Add a new server option, such as bdb_log_autoremove.

This should be made to be settable on the fly, as this is supported by BDB.
[5 Nov 2005 15:36] Jim Winstead
This is related to Bug #14655, which moves us to using DB_LOG_AUTOREMOVE instead of a custom mechanism for cleaning up the BDB log files.