moving parts.

The minimize machinery didn;t use the correct time units.

The incremental GC had some bugs that made it too conservative.

the actual caches.

to fail.

Fixed memory leak caused by incomplete PER_DEL.

out of memory can force aggressive cache behavior:

  cacheGC() -- do an incremental GC

  cacheFullSweep([dt]) -- Make a pass through objects in the cache
     removing unreferenced objects and, if dt > 0, deactivating
     objects accessed more than dt seconds ago.

  cacheMinimize([dt]) -- Make multiple passes through objects in the cache
     removing unreferenced objects and, if dt > 0, deactivating
     objects accessed more than dt seconds ago. Keep making passes
     until the cache size doesn;t change.

Added a coptimizations module.  The first optimization is
to provide an implementation of persistent_id in C.  This
routine, which is called extremely often while pickling was
found to be a significant bottleneck.

Fix a bug in object deactivation.
Overridden versions of _p_deactivate were not called.
This meant that BTrees were never deactivated.

Added coments regarding the pool lock and pool management.

exception.

lots of version commits.

Fixed a bug that caused bogus error logs saying that there were
bad references for objects created in uncommitted versions.

before the pack time *should* be and now are marked.  I was trying to
be cute about letting transactions before the pack time be packed.
This was bent and led to database corruption when these transactions
were undone.

occur.

affected objects were not properly recorded when there was a storage
error. This caused objects to be left in an invalid state.

checking for subtransactions.

on system crashes, causing apparent file corruption.  Code has been
added to check for this case and recover by truncating the file with a
log message.

Fixed bug in file-layout doc.

Added quota option.

Failures in _finish could cause the storage to hang because the
commit lock was not released.

should be a .py file, for dense folks like me that might miss that).

allowing the manager to see more than the very first 20 previous transactions.

forgotten even though they can be resurrected via undo.