BDB flags link.

This commit is contained in:
Gavin Henry 2008-04-11 21:48:35 +00:00
parent 19ad1e2a74
commit 831035f6be
2 changed files with 3 additions and 1 deletions

View File

@ -90,6 +90,7 @@ recommended:
* Log file removal - {{URL:http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/logfile.html}}
* Recovery procedures - {{URL:http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/recovery.html}}
* Hot failover - {{URL:http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/hotfail.html}}
* Complete list of Berkeley DB flags - {{URL:http://www.oracle.com/technology/documentation/berkeley-db/db/api_c/env_set_flags.html}}
Advanced installations can use special environment settings to fine-tune some
Berkeley DB options (change the log file limit, etc). This can be done by using

View File

@ -776,7 +776,8 @@ delete transaction log files as soon as their contents have been
checkpointed and they are no longer needed. Without this setting the
transaction log files will continue to accumulate until some other
cleanup procedure removes them. See the Berkeley DB documentation for the
{{EX:db_archive}} command for details.
{{EX:db_archive}} command for details. For a complete list of Berkeley DB
flags please see - {{URL:http://www.oracle.com/technology/documentation/berkeley-db/db/api_c/env_set_flags.html}}
Ideally the BDB cache must be
at least as large as the working set of the database, the log buffer size