Software: Apache/2.0.54 (Fedora). PHP/5.0.4 

uname -a: Linux mina-info.me 2.6.17-1.2142_FC4smp #1 SMP Tue Jul 11 22:57:02 EDT 2006 i686 

uid=48(apache) gid=48(apache) groups=48(apache)
context=system_u:system_r:httpd_sys_script_t 

Safe-mode: OFF (not secure)

/usr/share/doc/db4-devel-4.3.27/ref/upgrade.4.0/   drwxr-xr-x
Free 3.57 GB of 27.03 GB (13.19%)
                            Encoder    Tools    Proc.    FTP brute    Sec.    SQL    PHP-code    Update    Feedback    Self remove    Logout    

Viewing file:     mp.html (5.43 KB)      -rw-r--r--

Berkeley DB Reference Guide: Upgrading Berkeley DB Applications

Release 4.0: memp_XXX

The C API for the Berkeley DB Memory Pool subsystem was reworked in the 4.0 release as follows:

Applications calling any of the memp_register, memp_stat, memp_sync or memp_trickle functions should update those calls to use the enclosing DB_ENV handle's method (easily done as the first argument to the existing call is the correct DB_ENV handle).

In addition, the DB_ENV->memp_stat call has been changed in the 4.0 release to take a flags argument. To leave their historic behavior unchanged, applications should add a final argument of 0 to any calls made to DB_ENV->memp_stat.

Applications calling the memp_fopen function should update those calls as follows: First, acquire a DB_MPOOLFILE handle using the DB_ENV->memp_fcreate method. Second, if the DB_MPOOL_FINFO structure reference passed to the memp_fopen function was non-NULL, call the DB_MPOOLFILE method corresponding to each initialized field in the DB_MPOOL_FINFO structure. Third, call the DB_MPOOLFILE->open method method to open the underlying file. If the DB_MPOOLFILE->open method call fails, then DB_MPOOLFILE->close method must be called to destroy the allocated handle.

Applications calling the memp_fopen, memp_fclose, memp_fput, memp_fset, or memp_fsync functions should update those calls to use the enclosing DB_MPOOLFILE handle's method. Again, this is easily done as the first argument to the existing call is the correct DB_MPOOLFILE handle. With one exception, the calling conventions of the old and new interfaces are identical; the one exception is the DB_MPOOLFILE->close method, which requires an additional flag parameter that should be set to 0.

Copyright (c) 1996-2004 Sleepycat Software, Inc. - All rights reserved.