> > But what can be done if fsync returns before pages flushed?
>
> When you write out critical information, you keep earlier versions of
> it. On startup, if the critical information is corrupt, you use the
> earlier versions of it. This helps protect against the scenario I
> mentioned: a few disk blocks may not have been written when the power
> goes out.
>
> My impression is that that is what Tom is doing with his patches.
If fsync may return before data *actually* flushed then you may have
unlogged data page changes which breakes WAL rule and means corrupted
(inconsistent) database without ANY ABILITY TO RECOVERY TO CONSISTENT
STATE. Now please explain me how saving positions of two checkpoints
(what Tom is doing) can help here?
Vadim
