Olivier,

O> Er... Now I'm puzzled. You might well be right after all. I would have
O> to double check the doc and code to answer. Maybe someone will do
O> quicker than me.

I have meanwhile checked the config file itself, which has this to
say:

# ----------------------------
#
# How often the pages are flushed on disk
# (for databases with ForcedWrites=Off only)
#
# Number of unflushed writes which will accumulate before they are
# flushed, at the next transaction commit. For non-Win32 ports,
# the default value is -1 (Disabled)
#
# Type: integer
#
#MaxUnflushedWrites = 100

#
# Number of seconds during which unflushed writes will accumulate
# before they are flushed, at the next transaction commit. For non-Win32
# ports, the default value is -1 (Disabled)
#
# Type: integer
#
#MaxUnflushedWriteTime = 5

So it looks like forced writes off has become a less dangerous
situation in Fb 1.5. How much less I wouldn't want to find out,
though. :-)

While I am at it, does anyone know if MaxUnflushedWrites and
MaxUnflushedWriteTime are mutually exclusive? And, if not, which of
them takes precedence? I'd guess the first to happen, but guesswork
has never been my forte.

O> Anyway, I stand on my point that the speed of FB 1.5 on Win32 is
O> excellent, even with forced writes on

Yep.

Ciao
--
Nando mailto:nandod@...