> I believe Phil meant that the engine should allow its buffers to be
> flushed via an external request (by client app, for example). Don't like
> very much this proposal,
I don't really, especially as I need to support different DB OS's, and I
don't want to write differnt code for each.
> but do like the Phil's second one. In fact,
> flushing file buffers in the idle time (yes, it's one more low-priority
> thread) makes sense for me. It's still lazy writes, but much more reliable
> than the current behaviour on Windoze platforms.
If FB could call a 'flush' at a pre-cofigured time (every hour, every day
etc.), that would do the trick.
12:46am up 1 day, 7:35, 1 user, load average: 0.57, 0.31, 0.28