memp_sync
memp_sync |
|
#include <db.h>int memp_sync(DB_ENV *env, DB_LSN *lsn);
The memp_sync function ensures that any modified pages in the pool with log sequence numbers less than the lsn argument are written to disk. If lsn is NULL all modified pages in the pool are flushed.
The primary purpose of the memp_sync function is to enable a transaction manager to ensure, as part of a checkpoint, that all pages modified by a certain time have been written to disk. Pages in the pool that cannot be written back to disk immediately (e.g., that are currently pinned) are written to disk as soon as it is possible to do so. The expected behavior of the Berkeley DB or other transaction subsystem is to call the memp_sync function and then, if the return indicates that some pages could not be written immediately, to wait briefly and retry again with the same log sequence number until the memp_sync function returns that all pages have been written.
To support the memp_sync functionality, it is necessary that the pool functions know the location of the log sequence number on the page for each file type. This location should be specified when the file is opened using the memp_fopen function. It is not required that the log sequence number be aligned on the page in any way.
The memp_sync function returns a non-zero error value on failure, 0 on success, and returns DB_INCOMPLETE if there were pages which need to be written but which memp_sync was unable to write immediately. In addition, if memp_sync returns success, the value of lsn will be overwritten with the largest log sequence number from any page which was written by memp_sync to satisfy this request.
The memp_sync function may fail and return a non-zero error for the following conditions:
The memp_sync function was called without logging having been initialized in the environment.
The memp_sync function may fail and return a non-zero error for errors specified for other Berkeley DB and C library or system functions. If a catastrophic error has occurred, the memp_sync function may fail and return DB_RUNRECOVERY, in which case all subsequent Berkeley DB calls will fail in the same way.
|
|