On 04/14/2010 03:30 AM, Nitro wrote:
Am 14.04.2010, 04:39 Uhr, schrieb Tim Peterstim.pet...@gmail.com:
[Nitro]
...
I wonder if _commit is really *that* slow
Six years ago I timed factor-of-100 speed differences due to using MS
_commit() on WinXP at the time:
On 4/14/10 08:24 , Christian Theune wrote:
I'm pretty sure it's not. IIRC fsync is defined by POSIX and absolutely
requires the implementor to flush data physically to disk ensuring its
persistency. If that doesn't hold true then all transactions are borked.
That was the problem with fsync on
Am 14.04.2010, 09:24 Uhr, schrieb Christian Theune c...@gocept.com:
What I don't really get is why you should never use None on windows.
As
far as I can judge from the various transaction rates in the thread Tim
mentioned, fsync is just a no-op on linux anyways (depending on the
specific
On Wed, Apr 14, 2010 at 11:52 AM, Nitro ni...@dr-code.org wrote:
Yes, in my case it's nothing critical or related to money. If there's a
hardware outage a day of work is lost at worst. In case of corruption
(which can happen also without fsync as data within the file can just be
garbled) you
Am 14.04.2010, 14:45 Uhr, schrieb Hanno Schlichting ha...@hannosch.eu:
Usually you will only loose the last transaction and not a days of
work. The Data.fs is an append-only file, with one transaction
appended after another. If there's a garbled or incomplete write,
you'll typically loose the
On Mon, Apr 12, 2010 at 6:29 AM, Tres Seaver tsea...@palladion.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Implements '--kill-old-on-full' command line switch for repozo, which
removes older full / incremental backups on successful completion of a
full backup.
