durusmail: durus-users: New release of "BerkeleyDB Backend Storage Engine for DURUS"
New release of "BerkeleyDB Backend Storage Engine for DURUS"
2006-11-21
Jesus Cea
New release of "BerkeleyDB Backend Storage Engine for DURUS"
Jesus Cea
2006-11-21
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

More info in
http://www.argo.es/~jcea/programacion/durus-berkeleydbstorage.htm

This release requires Durus 3.6. Already existing storages will be
upgraded automatically and instantaneously (non-stop), and will *NOT* be
usable in previous storage releases

UPGRADE NOTES:

    * This release REQUIRES Durus 3.6 or higher.

    * Storage databases created with this release are not compatible
with previous releases.

      First time you use this release to open a storage database created
by previous releases, it will be transparently "upgraded" to current
format, so:

          o The storage will become incompatible with previous releases.

          o In order to be able to upgrade the storage, you can't open
it in "read only" mode. Once upgraded, you can use "read only" mode freely.

          o The upgrade process doesn't take any RAM.

          o If the upgrade process is aborted (program quits, crashes,
machine reboot, etc), the database will be stable and clean. That is,
the upgrade process is transactional and SAFE.

          o The upgrade process will be "instantaneous".

    * A new checkpoint policy object:
"berkeleydb_storage.checkpoint_thread_final_checkpoint".

      This checkpoint policy does a forced checkpoint when closing the
storage. This would slowdown storage shutdown, but speed up storage
initializacion.


CHANGES:

# 20061117 - r275 - jcea@argo.es

Shy first implementation of "sync" feedback feature of Durus 3.6.

Since this point, this Storage Engine requires Durus 3.6 and up.

# 20061117 - r274 - jcea@argo.es

Full implementations of "garbage_collection_noop" and
"garbage_collection_inline" policy objects.

# 20061117 - r264 - jcea@argo.es

A late compatibility fix for Durus 3.6.

This fix requires a (instantaneous) storage upgrade.

# 20061117 - r262 - jcea@argo.es

Initial support for a garbage collection policy objects.

# 20061116 - r257 - jcea@argo.es

A new checkpoint policy object:
"berkeleydb_storage.checkpoint_thread_final_checkpoint".

# 20061116 - r251 - jcea@argo.es

More gentle database closing if the program closes the storage handle
and then dies without giving an oportunity to the garbage collector.

# 20061116 - r250 - jcea@argo.es

The storage did a database recover even if asked to not do it.

# 20061116 - r246 - jcea@argo.es

Do some minor changes for compatibility with just released Durus 3.6.

# 20061116 - r245 - jcea@argo.es

"KNOW_HOW-DURUS" updated to Durus 3.6.

- --
Jesus Cea Avion                         _/_/      _/_/_/        _/_/_/
jcea@argo.es http://www.argo.es/~jcea/ _/_/    _/_/  _/_/    _/_/  _/_/
jabber / xmpp:jcea@jabber.org         _/_/    _/_/          _/_/_/_/_/
                               _/_/  _/_/    _/_/          _/_/  _/_/
"Things are not so easy"      _/_/  _/_/    _/_/  _/_/    _/_/  _/_/
"My name is Dump, Core Dump"   _/_/_/        _/_/_/      _/_/  _/_/
"El amor es poner tu felicidad en la felicidad de otro" - Leibniz
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRWJF2plgi5GaxT1NAQJ6KgP8CLN124cgJpiFZG+xgH8I6Gzd35dasOfZ
pY9hh7r9Vfub/kibWVOzlGIDZ7GQJL60j+qPj5y/7ef9AyFJxcj9ft9zdNRLHtTm
4aqhmnmINCvqeQxKWceGkXfvX0hFZqGOGEt7vDTmp914pad4hFKx7EgcbSDnYTjA
peK+bcLF4ak=
=Qh/e
-----END PGP SIGNATURE-----
reply