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

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 (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-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

pgsql-bugs by date

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

pgsql-patches by date

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

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