Re: Permission denied on fsync / Win32 (was right sibling is not next child) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Permission denied on fsync / Win32 (was right sibling is not next child)
Date
Msg-id 28966.1144953420@sss.pgh.pa.us
Whole thread Raw
In response to Re: Permission denied on fsync / Win32 (was right sibling is not next child)  ("Magnus Hagander" <mha@sollentuna.net>)
List pgsql-bugs
"Magnus Hagander" <mha@sollentuna.net> writes:
> BTW, win32 sometimes has a bad habit of returning access denied for
> other things as well - in some caes you can get access denied instead of
> sharing violation, and you can often get it from AV and firewalls and
> such.

Looking at the fsync code in md.c, I note that it's designed to disregard
file-not-found (ENOENT).  Are there any cases in which win32 might
return EPERM for scenarios that a sane person would call file-not-found?

            regards, tom lane

pgsql-bugs by date:

Previous
From: "Magnus Hagander"
Date:
Subject: Re: Permission denied on fsync / Win32 (was right sibling is not next child)
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #2386: pg_restore doesn't restore large objects