diff options
| author | Andreas Baumann <abaumann@yahoo.com> | 2012-04-19 07:48:40 +0200 |
|---|---|---|
| committer | Andreas Baumann <abaumann@yahoo.com> | 2012-04-19 07:48:40 +0200 |
| commit | 4f806ad00f8179e0007bcbc3d6114cddae0a533b (patch) | |
| tree | f5b1b3c47c05fbf0cfd1a02368c86902bb2356c6 /DEVELOPERS | |
| parent | dda8a2b8a6be653e60ae92a0841494e0521201a8 (diff) | |
| download | pgfuse-4f806ad00f8179e0007bcbc3d6114cddae0a533b.tar.gz pgfuse-4f806ad00f8179e0007bcbc3d6114cddae0a533b.tar.bz2 | |
removed size from PgFuseFile, update metadata on every write
Diffstat (limited to 'DEVELOPERS')
| -rw-r--r-- | DEVELOPERS | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -65,6 +65,10 @@ COPY FROM and COPY to as a fast, non-transactional mode? Pad blocks in data or not? Or all but the last one, allowing very small files to be stored efficiently. +How to tune the block sizes? What factors influence the experiment? +At the moment we store padded blocks of fixes size (STANDARD_BLOCK_SIZE), +not really sure if that is good or bad. + Directory tree in database -------------------------- |