summaryrefslogtreecommitdiff
path: root/DEVELOPERS
diff options
context:
space:
mode:
authorAndreas Baumann <abaumann@yahoo.com>2012-04-19 11:14:33 +0200
committerAndreas Baumann <abaumann@yahoo.com>2012-04-19 11:14:33 +0200
commita5923caf474983e14477498117fabb041805fd04 (patch)
treee6a40a174d064acb2c7ab5a3b1e6366193b8b7d8 /DEVELOPERS
parent4a88c817b17498e72a95589f887197ab43edc491 (diff)
downloadpgfuse-a5923caf474983e14477498117fabb041805fd04.tar.gz
pgfuse-a5923caf474983e14477498117fabb041805fd04.tar.bz2
added first simple transaction policy (per FUSE operation)
Diffstat (limited to 'DEVELOPERS')
-rw-r--r--DEVELOPERS14
1 files changed, 14 insertions, 0 deletions
diff --git a/DEVELOPERS b/DEVELOPERS
index 032d9cb..e350530 100644
--- a/DEVELOPERS
+++ b/DEVELOPERS
@@ -5,6 +5,8 @@ Internal documentation for developers
Design decisions
Storage of binarydata
Directory tree in database
+ Transaction Policies
+ Self-containment
Testing
Coding guidelines
@@ -79,6 +81,18 @@ Naive implementation
TODO...
+Transaction Policies
+--------------------
+
+Fundamental querstion: What file operations should form a database transaction?
+
+one extreme: isolate threads and all file operations in one transaction
+other extreme: "autocommit" (every write, every read, etc.), this allows
+for parallel usage, as long as we have ref_count and an exclusive
+locking, this extreme makes no sense
+
+specify transaction strategy as mount options?
+
Self-containment
----------------