I have been using Darcs to version-control the ASCII dumps of a Postgresql
database. The dump is ~ 15 MB in size.
After recording 7 changes:
size created name
-----------------------------------------------------------------------------------------------------------
2592 2006-07-24 13:51
../_darcs/patches/20060724195018-249ed-aecd0695707e36951919dddcdd43bb81509cd750.gz
491 2006-07-12 13:29
../_darcs/patches/20060712192854-249ed-ec7d8de7de48fc30549ad3aa619cef1e1c55a864.gz
355 2006-07-12 10:31
../_darcs/patches/20060712162805-249ed-5502f88756b1246a7cacb4090c1a3d567a205699.gz
762 2006-06-26 15:15
../_darcs/patches/20060626211423-249ed-f94effae993295d3d7d3fdd2de3abb52233f5b0e.gz
1414 2006-06-21 11:08
../_darcs/patches/20060621170807-249ed-8f3f3d5ca9b45a0ada993412ff795a5488537326.gz
1622055 2006-06-21 11:00
../_darcs/patches/20060621170029-249ed-44cf0ae1e0ed7b8b12f26f483de8ac42d67fd144.gz
I cannot record the eighth, because Darcs grabs for more and more memory
and hits a ceiling around 1 GB.
I have worked around this by `darcs mv'ing the old file and starting a new
dump, which is OK for my purposes, but I wonder whether this is expected
behaviour.
If Darcs hung up for an infinite amount of time, I wouldn't be surprised
(or only a bit, as I don't expect a vast number of overlapping changes
when I change only a few of the database tables), but I haven't
encountered this memory problem before.
darcs-1.0.7pre1 (unknown)
W o l f g a n g
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
