aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBen Johnson <benbjohnson@yahoo.com>2015-03-27 15:27:32 -0600
committerBen Johnson <benbjohnson@yahoo.com>2015-03-27 15:27:32 -0600
commit9d1dd87a79929d2d82b264a4163b745fd3c340e9 (patch)
tree81e35cfcf58222d60ae4eee9c5d11a4d5ce6c16a
parentMerge pull request #334 from funkygao/master (diff)
downloaddedo-9d1dd87a79929d2d82b264a4163b745fd3c340e9.tar.gz
dedo-9d1dd87a79929d2d82b264a4163b745fd3c340e9.tar.xz
README
Document use of free pages and page reclamation works.
-rw-r--r--README.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/README.md b/README.md
index 18ba570..691f9f9 100644
--- a/README.md
+++ b/README.md
@@ -550,6 +550,12 @@ Here are a few things to note when evaluating and using Bolt:
However, this is expected and the OS will release memory as needed. Bolt can
handle databases much larger than the available physical RAM.
+* Because of the way pages are laid out on disk, Bolt cannot truncate data files
+ and return free pages back to the disk. Instead, Bolt maintains a free list
+ of unused pages within its data file. These free pages can be reused by later
+ transactions. This works well for many use cases as databases generally tend
+ to grow. However, it's important to note that deleting large chunks of data
+ will not allow you to reclaim that space on disk.
## Other Projects Using Bolt