Skip site navigation (1) Skip section navigation (2)

Re: Permission denied on fsync / Win32 (was right sibling is not next child)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Magnus Hagander" <mha(at)sollentuna(dot)net>
Cc: "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: Permission denied on fsync / Win32 (was right sibling is not next child)
Date: 2006-04-13 18:37:00
Message-ID: 28966.1144953420@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
"Magnus Hagander" <mha(at)sollentuna(dot)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

In response to

pgsql-bugs by date

Next:From: Bruce MomjianDate: 2006-04-13 19:39:47
Subject: Re: BUG #2386: pg_restore doesn't restore large objects
Previous:From: Magnus HaganderDate: 2006-04-13 18:33:46
Subject: Re: Permission denied on fsync / Win32 (was right sibling is not next child)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group