Re: BUG #2712: could not fsync segment: Permission - Mailing list pgsql-bugs

From Magnus Hagander
Subject Re: BUG #2712: could not fsync segment: Permission
Date
Msg-id 6BCB9D8A16AC4241919521715F4D8BCEA0FCC2@algol.sollentuna.se
Whole thread Raw
In response to Re: BUG #2712: could not fsync segment: Permission  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
> > i've installed Filemon=20
> > (http://www.sysinternals.com/Utilities/Filemon.html)
> > now. this gives more insight what happens to the file.
> > ...
> > D:\DB\PostgreSQL-8.2\data\base\3964774\6422806 DELETE PEND Options:=20
> > Open
> > Access: 0012019F
>=20
> This is quite interesting, because it says that Filemon knows=20
> how to distinguish a "delete pending" error from other=20
> errors.  If we could do that, then my prior worries about=20
> ignoring all EACCES errors would go away.  What's it looking=20
> at exactly?

filemon is a kernel mode filter driver. So it's looking at kernel-only
datastructures. AFAIK, there is no way to see that from userspace.

//Magnus

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #2712: could not fsync segment: Permission
Next
From: "Thomas H."
Date:
Subject: Re: could not rename xlog (was: BUG #2712)