Re: BUG #2712: could not fsync segment: Permission

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Thomas H(dot)" <me(at)alternize(dot)com>
Cc: "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>, pgsql-bugs(at)postgresql(dot)org, "Magnus Hagander" <mha(at)sollentuna(dot)net>
Subject: Re: BUG #2712: could not fsync segment: Permission
Date: 2006-10-24 05:58:54
Message-ID: 4142.1161669534@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

"Thomas H." <me(at)alternize(dot)com> writes:
> i've installed Filemon (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: Open
> Access: 0012019F

This is quite interesting, because it says that Filemon knows how to
distinguish a "delete pending" error from other errors. If we could
do that, then my prior worries about ignoring all EACCES errors would
go away. What's it looking at exactly?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2006-10-24 06:05:28 Re: BUG #2712: could not fsync segment: Permission
Previous Message Tom Lane 2006-10-24 04:29:05 Re: BUG #2701: PQserverVersion function missing

Browse pgsql-patches by date

  From Date Subject
Next Message Magnus Hagander 2006-10-24 06:05:28 Re: BUG #2712: could not fsync segment: Permission
Previous Message Alvaro Herrera 2006-10-24 01:22:50 Re: [PATCHES] smartvacuum() instead of autovacuum