summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-12-02 19:11:28 +0000
committerGravatar admin <admin@branchable.com>2013-12-02 19:11:28 +0000
commit6d58a12aeb4314ff7fe5c10fc9e6fcff4fc12ad1 (patch)
tree1251c22f2123badb1ebdc9bfe5e947817716b078
parentbbb532c571782a0898974657ed820da376a85658 (diff)
Added a comment
-rw-r--r--doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_3_c6c8d3c84afa497bfdfe25b492dac5b9._comment12
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_3_c6c8d3c84afa497bfdfe25b492dac5b9._comment b/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_3_c6c8d3c84afa497bfdfe25b492dac5b9._comment
new file mode 100644
index 000000000..17d7a3aab
--- /dev/null
+++ b/doc/bugs/incremental_fsck_should_not_use_sticky_bit/comment_3_c6c8d3c84afa497bfdfe25b492dac5b9._comment
@@ -0,0 +1,12 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.64"
+ subject="comment 3"
+ date="2013-12-02T19:11:27Z"
+ content="""
+HongoDB doesn't build with current hackage.
+
+keyvaluehash passed some inital load etc tests. The inability to delete old keys/values might not be a significant problem.
+
+However I don't think it has any ACID guarantees; eg a crash at the wrong time could leave the database in some inconsistent state. <https://github.com/Peaker/keyvaluehash/issues/1>
+"""]]