"Peter Brant" <Peter.Brant@wicourts.gov> writes:
> FWIW, we were bitten by the fsync problem which you noticed too.
> Unfortunately we were never able to track down a cause (see the mailing
> list archives). They are separate problems though.
Actually, now that I look back in the archives, I think we had theorized
that the fsync errors come from attempting to fsync a file that's
already been deleted but some backend still has a reference to.
Apparently that leads to EACCES instead of ENOENT (which the code is
already prepared to expect).
http://archives.postgresql.org/pgsql-bugs/2006-04/msg00215.php
regards, tom lane
