| Bug #14655 | Use DB_LOG_AUTOREMOVE flag instead of noticecall customization to BDB | ||
|---|---|---|---|
| Submitted: | 4 Nov 2005 19:11 | Modified: | 3 Dec 2005 3:32 |
| Reporter: | Jim Winstead | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: BDB | Severity: | S3 (Non-critical) |
| Version: | 5.1 | OS: | Any (All) |
| Assigned to: | Jim Winstead | CPU Architecture: | Any |
[4 Nov 2005 19:32]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/31955
[8 Nov 2005 0:31]
Bugs System
A patch for this bug has been committed. After review, it may be pushed to the relevant source trees for release in the next version. You can access the patch from: http://lists.mysql.com/internals/32066
[2 Dec 2005 20:49]
Georg Richter
see also bug #14656
Description: Instead of our patch to the BDB library to add support for a callback to be delivered when BDB has switched to a new log file, which we use to then delete the old log file, we should simply use the new DB_LOG_AUTOREMOVE flag that became available in BDB 4.3. How to repeat: set max_allowed_packet = 11*1024*1024; create table t1 (a int primary key, b longblob) engine=bdb; insert into t1 values (1, repeat(' ', 10*1024*1024)); drop table t1; make sure that the first bdb log file has been deleted. Suggested fix: Remove unnecessary code.