> > The error messages refer to the old relfilenode (in 3 out of 3=20
> > occurrences today).
>=20
> So it'd seem the problem is with fsync on recently-deleted files.
> Is it possible that we are getting EACCES (ERROR_SHARING_VIOLATION
> maybe) in the situation where we try to fsync a file that's=20
> been unlinked but isn't fully gone yet due to open handles?
I think that sounds "reasonable". Not as in a reasonable thing to do,
but as a reasonable thing to expect from the win32 api.
//Magnus
