Resizing

cuprate_database itself does not handle memory map resizes automatically (for database backends that need resizing, i.e. heed/LMDB).

When a user directly using cuprate_database, it is up to them on how to resize. The database will return RuntimeError::ResizeNeeded when it needs resizing.

However, cuprate_database exposes some resizing algorithms that define how the database's memory map grows.

Last change: 2024-10-02, commit: a003e05