Subject | Re: [firebird-support] Async writes/forced writes |
---|---|
Author | Ivan Prenosil |
Post date | 2005-03-23T13:38:14Z |
> - Is it true that this feature exists already, in v1.5?Look into "firebird.conf", it contains lot of comments,
and afaik it should not contain unimplemented switches ...
Ivan
----- Original Message -----
From: "Kjell Rilbe" <kjell.rilbe@...>
To: <undisclosed-recipients:>
Sent: Wednesday, March 23, 2005 2:28 PM
Subject: [firebird-support] Async writes/forced writes
>
> Hi,
>
> In a comment to a feature request, Dmitry Yemanov writes this:
>
> > Since v1.5, async writes are controlled by the engine. The cache
> > manager flushes dirty pages accordingly to MaxUnflushedWrites and
> > MaxUnflushedWriteTime configuration parameters. This gives you a
> > compromise between fast-but-never-flushed (old FW=OFF) and
> > low-but-reliable (FW=ON) page write mechanisms.
>
> I've never heard this before. What I've *repeatedly* heard is that on
> Win32 I should turn forced writes on to avoid db corruption due to
> potentially indefinately delayed cache flushes (caused by the OS).
>
> So, is it true? Specifically:
>
> - Is it true that this feature exists already, in v1.5?
>
> - Is it true that it really works on Win32?
>
> - Any risks I should be aware of, apart from the obvious one: risk of DB
> corruption on crash/powerdown during MaxUnflushedWriteTime?
>
> Thanks,
> Kjell